| CDT CVS integration with managed makefiles [message #166975] |
Thu, 30 March 2006 10:28  |
Eclipse User |
|
|
|
Originally posted by: nwong.kancharla.com
I'm using Eclipse CDT and I have several managed makefile C++ programs for
running on servers. I use CVS to help distribute the code amongst the
programmers.
On the servers, when I checkout the CVS project, the generated makefile is
NOT included. Therefore, I can't compile it on the server over an ssh
terminal.
I have tried using a post build procedure to copy makefile and *.mk into
../, which makes them part of the CVS, but the subdirs.mk always fails to
work properly when not in the ./Debug or ./Release folders.
Is there some way to include the Makefile in the CVS commit from a managed
make project?
Please help!
Nicholas Wong
|
|
|
| Re: CDT CVS integration with managed makefiles [message #167245 is a reply to message #166975] |
Mon, 03 April 2006 13:57  |
| Eclipse User |
|
|
|
Nicholas Wong wrote:
> I'm using Eclipse CDT and I have several managed makefile C++ programs
> for running on servers. I use CVS to help distribute the code amongst
> the programmers.
>
> On the servers, when I checkout the CVS project, the generated makefile
> is NOT included. Therefore, I can't compile it on the server over an ssh
> terminal.
>
> I have tried using a post build procedure to copy makefile and *.mk into
> ./, which makes them part of the CVS, but the subdirs.mk always fails to
> work properly when not in the ./Debug or ./Release folders.
>
>
> Is there some way to include the Makefile in the CVS commit from a
> managed make project?
>
> Please help!
>
> Nicholas Wong
>
I posted a solution to a similar problem (see 3/22, "Export Project..."
post). It was something of a hack, but might serve as a starting point
for you.
I think you can always navigate to the makefiles and add them to CVS
manually. That might not be suitable, as folders get added etc. A
post-build step that creates a tar file containing the Release and Debug
folders (only containing makefile and *.mk, along with the
makefile.defs, makefile.target and makefile.init in the root folder, if
present) would do the trick. Drop that tar file into your root folder
and add IT to CVS?
Another possibility: take a look at this article....
http://www-128.ibm.com/developerworks/eserver/library/es-uni x-eclipse/index.html
The article shows how to use Ant to automate a Standard Make project.
That's not what you have, but Ant offers some nice options. For example,
I have a workspace where I develop a library, a server application and a
client. Each is in its own project (using managed build). I created a
separate project (a Simple Project) and created an ant build.xml file to
tar the server project and library. Ant offers actions which can push
those files (using ftp or scp) to another machine. In my case this is
preferable because the machines where I test do not have eclipse
installed. I just unzip there and build.
I don't have time now to offer more of an example of this. If you're
interested I can post what I have ....
dan
|
|
|
Powered by
FUDForum. Page generated in 0.02785 seconds
Home