[Premake-users] Code::Blocks dependency problems
On GitHub now!
Brought to you by:
starkos,
ttk-bandit
From: Ryan P. <rpu...@gm...> - 2006-11-22 05:51:43
|
1. When using the syntax: package.links = { "PackageB" } it puts the full output name with path as the link settings. There are 2 problems with that. a) If it is a dll or lib Code::Blocks doesn't find the library to link to if it has an extension. Ex. libticpp.a (Doesn't work) libticpp (WORKS) b) It uses the output directory set in the premake script specific to the project. This doesn't help when the main project has a different location. In other words, it doesn't fix the path to be relative to the main project that "links" the subprojects. 2. Dependencies are not set at all in Code::Blocks. (Not tested in GNU target yet) When I generate from a main premake script and include a bunch of other packages, and inside the main project I add the packages to the "links" configuration it doesn't seem to trigger the dependancies to build first. I also checked the "Project dependanies" dialog in Code::Blocks and none of the projects were selected. -- Regards, Ryan RJP Computing |