addon_config.mk equivalent codes? about projectgenerator

[danoli3]

For example I have an addon that has about 30,000 headers. I tried to add the the directory to the ADDON_INCLUDES =, however I noticed it was adding them all to the project (with projectGenerator -v)

So usually this would just be a single folder directory in the HEADER_SEARCH_PATHS and keep it all out of the project.

[ofZach]

I don't think we have header search paths as part of addon_config.mk.

this is what we do parse:

https://github.com/openframeworks/projectGenerator/blob/master/ofxProjectGenerator/src/addons/ofAddon.cpp#L187-L290

we do most things primarily via file system, addon_config.mk augments that by allowing you to specifiy exactly the order / exclude things, etc.

[danoli3]

projectGenerator still going 2 hours later.... lol!

I might add that command if that is okay

[ofZach]

ha that's pretty insane.

I think it's possible to do this, but adding a new feature across all project types can take some time to get right. happy to walk you through it and explain what to look at.

[arturoc]

HEADER_SEARCH_PATHS is ADDON_INCLUDES in addons_config.mk

the way it works is by parsing the filesystem first. then you can overwrite that values with:

ADDON_INCLUDES = some_path
ADDON_INCLUDES += som_otherPath
...

or add some path to the parsed from the filesystem:

ADDON_INCLUDES += some_otherPath

so the = overwrites even the filesystem parsed paths and the += adds new values

[arturoc]

also if you are refering to the header files rather than the search paths that's in ADDONS_SOURCES, it works the same it parses the filesystem and then you can overwrite. so if you only want to add libs/boost/include/boost.hpp:

ADDON_SOURCES = libs/boost/include/boost.hpp

if you had some source in src you'll need to readd it manually with ADDON_SOURCES

[ofZach]

(sorry for the misinformation !)

[arturoc]

:)