openframeworks / openframeworks/projectGenerator

addon_config.mk equivalent codes?

Open
#65 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
CSS
Stars
90
Forks
79
Avg merge
2d 9h
Merged PRs (30d)
5

Description

I can't find this documented anywhere.

What are the Addon_config equivalents for the following Xcode commands:
LIBRARY_SEARCH_PATHS (Library Search Paths)
HEADER_SEARCH_PATHS (Header Search Paths)


Spec:


# dependencies with other addons, a list of them separated by spaces 
    # or use += in several lines
    # ADDON_DEPENDENCIES =

    # include search paths, this will be usually parsed from the file system
    # but if the addon or addon libraries need special search paths they can be
    # specified here separated by spaces or one per line using +=
    #ADDON_INCLUDES = 

    # any special flag that should be passed to the compiler when using this
    # addon
    # ADDON_CFLAGS =

    # any special flag that should be passed to the linker when using this
    # addon, also used for system libraries with -lname
    # ADDON_LDFLAGS =

    # linux only, any library that should be included in the project using
    # pkg-config
    # ADDON_PKG_CONFIG_LIBRARIES =

    # osx/iOS only, any framework that should be included in the project
    # ADDON_FRAMEWORKS =

    # source files, these will be usually parsed from the file system looking
    # in the src folders in libs and the root of the addon. if your addon needs
    # to include files in different places or a different set of files per platform
    # they can be specified here
    # ADDON_SOURCES =

    # some addons need resources to be copied to the bin/data folder of the project
    # specify here any files that need to be copied, you can use wildcards like * and ?
    # ADDON_DATA = 

    # when parsing the file system looking for libraries exclude this for all or
    # a specific platform
    # ADDON_LIBS_EXCLUDE =

         # binary libraries, these will be usually parsed from the file system but some 
    # libraries need to passed to the linker in a specific order 
    ADDON_LIBS =



Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the ADDON_INCLUDES, ADDON_CFLAGS, and ADDON_LDFLAGS entries shown in the addon_config.mk specification, then compare them with Xcode's LIBRARY_SEARCH_PATHS and HEADER_SEARCH_PATHS. Document the corresponding settings and their intended use in the addon_config.mk documentation.

Written by the indexing model from the issue text.

Assessment

Domain
build-system, documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.