| persisting make targets [message #89145] |
Fri, 12 December 2003 14:48  |
Eclipse User |
|
|
|
Originally posted by: kcoleman.us.ibm.com
I have a C/C++ project that lives in CVS. It targets Windows and multiple
Unix flavors, so it has an nmake-based Windows makefile and a gmake-based
Unix makefile. I would like to embed the knowledge of how to do both
flavors of build in my project in CVS.
I used Create Make Target to create Unix and Windows build commands, using
the appropriate makefiles. It was the only way I could find to enable
multi-platform make commands for a single project. It seems to work fine.
However, unlike tweaking the make command via the project properties
dialog, Create Make Target creates a workspace-specific setting (e.g. goes
into the .metadata dir), not a project property, even though they're
decidedly project specific. The upshot is I can't persist these targets in
CVS by checking in the .project or .cdtproject file. And hence, cannot
make it team-wide.
Is "Create Make Target" the correct way to handle disparate build
commands? If so, how can I bind this knowledge to the project? I'm hoping
I've just missed something totally obvious to even the most casual
observer. :-)
Thanks.
-Kim
|
|
|
| Re: persisting make targets [message #89498 is a reply to message #89145] |
Mon, 15 December 2003 11:32  |
| Eclipse User |
|
|
|
Originally posted by: alain.nowhere.ca
kcoleman@us.ibm.com wrote:
> I have a C/C++ project that lives in CVS. It targets Windows and multiple
> Unix flavors, so it has an nmake-based Windows makefile and a gmake-based
> Unix makefile. I would like to embed the knowledge of how to do both
> flavors of build in my project in CVS.
> I used Create Make Target to create Unix and Windows build commands, using
> the appropriate makefiles. It was the only way I could find to enable
> multi-platform make commands for a single project. It seems to work fine.
> However, unlike tweaking the make command via the project properties
> dialog, Create Make Target creates a workspace-specific setting (e.g. goes
> into the .metadata dir), not a project property, even though they're
> decidedly project specific. The upshot is I can't persist these targets in
> CVS by checking in the .project or .cdtproject file. And hence, cannot
> make it team-wide.
> Is "Create Make Target" the correct way to handle disparate build
> commands? If so, how can I bind this knowledge to the project? I'm hoping
> I've just missed something totally obvious to even the most casual
> observer. :-)
8-)
It is in the planning for CDT-2.0(hopefully).
Exporting this to a file that can be save and reread.
|
|
|
Powered by
FUDForum. Page generated in 0.07499 seconds
Home