amrein Messages: 278 Registered: August 2008 Location: France
Experienced Member
No downside but it's ugly?
Better to:
- add another array in Package class:
Array<OptItem> library_path;
- add in PackageEditor::PackageEditor()
Add("Internal include path", actual.include);
Add("Internal library path", actual.library_path);
- Make actual.include like other options in Package Organizze (I mean, with rw access to 'When' textfield so it can be flag activated/distribution specific)
- Then use those Package variables to fill Makefiles and default .bm files if those flags are active
?
I didn't find where "Internal include" (package.include) is used in TheIDE, so I renamed it "Internal include path".
Members
Pages
Help
Register
Login
Home
?
