-
Notifications
You must be signed in to change notification settings - Fork 77
Multiple flags are correctly read into VS projects, added support for preprocessor definitions in addons #214
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Changes from 3 commits
4a38a3f
b1ef172
3ff92b5
37b5cbf
732c210
cb10c7b
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -261,10 +261,15 @@ void ofAddon::parseVariableValue(string variable, string value, bool addToValue, | |
addReplaceStringVector(includePaths,value,addonRelPath,addToValue); | ||
} | ||
|
||
|
||
if(variable == "ADDON_CFLAGS"){ | ||
addReplaceStringVector(cflags,value,"",addToValue); | ||
} | ||
|
||
if (variable == "ADDON_PREPROCESSOR_DEFINITIONS") { | ||
addReplaceStringVector(preprocessorDefinitions, value, "", addToValue); | ||
} | ||
|
||
if(variable == "ADDON_CPPFLAGS"){ | ||
addReplaceStringVector(cppflags,value,"",addToValue); | ||
} | ||
|
@@ -310,7 +315,7 @@ void ofAddon::parseVariableValue(string variable, string value, bool addToValue, | |
} | ||
|
||
if(variable == "ADDON_DATA"){ | ||
addReplaceStringVector(data,value,"",addToValue); | ||
addReplaceStringVector(data,value,addonRelPath,addToValue); | ||
|
||
} | ||
|
||
if(variable == "ADDON_LIBS_EXCLUDE"){ | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -45,6 +45,7 @@ class ofAddon { | |
std::vector < std::string > frameworks; // osx only | ||
std::vector < std::string > data; | ||
std::vector < std::string > defines; | ||
std::vector < std::string > preprocessorDefinitions; // vs only | ||
brinoausrino marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
||
// metadata | ||
std::string name; | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this reference to ADDON_PREPROCESSOR_DEFINITIONS should go as well
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so, then adding ADDON_PREPROCESSOR_DEFINITIONS is useful?
Since I changed
additionalOptions = items[i].node().child("ClCompile").child("AdditionalOptions");
for
additionalOptions = items[i].node().child("ClCompile").child("PreprocessorDefinitions");
Should we leave it like this or should we use the seperate preprocessor flag?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no sorry, what i meant is it should go away
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
already is in the latest commit