RE: [cdt-dev] FTP-transfer after building .exe

["Recoskie, Chris" <crecoskie@xxxxxx>]

Either that or create your own makefile generator.  You could use the existing GNU makefile generator as a base and just customize the creation of the link rules.  This is probably your best bet if you cannot afford to wait.

___________________________________________
 
Chris Recoskie
Software Designer
IDE Frameworks Group
Texas Instruments, Toronto
 
 

> -----Original Message-----
> From: cdt-dev-admin@xxxxxxxxxxx [mailto:cdt-dev-admin@xxxxxxxxxxx] On
> Behalf Of Treggiari, Leo
> Sent: Wednesday, February 16, 2005 10:45 AM
> To: cdt-dev@xxxxxxxxxxx
> Subject: RE: [cdt-dev] FTP-transfer after building .exe
> 
> I think that you will have to wait until CDT 3.0.  MBS currently has some
> significant special case code regarding the link step.
> 
> Regards,
> Leo
> 
> -----Original Message-----
> From: cdt-dev-admin@xxxxxxxxxxx [mailto:cdt-dev-admin@xxxxxxxxxxx] On
> Behalf Of Ploett Norbert
> Sent: Wednesday, February 16, 2005 10:29 AM
> To: cdt-dev@xxxxxxxxxxx
> Subject: [cdt-dev] FTP-transfer after building .exe
> 
> Hello all,
> 
> I am using eclipse for C/C++ development for an embedded platform. After
> building the .exe target it must be moved to the target using ftp. I would
> like eclipse to automatically move the .exe to the target as part of the
> managed build.
> 
> This was my scheme (which failed, so far):
> 
> 1. Get the C sources translated to .o with the gcc compiler (works fine).
> 2. Get the .o files linked to .exe with gcc (works fine, too).
> 3. Define another tool in the toolchain, a shell script which will take
> .exe as source, transfer it to the target, and, on success creates a
> little .txt file to let make know that even the last stage of the build
> succeeded.
> 
> I managed to create a plugin which defines a new project type, containing
> my own definitions for configuration, tool chain and "ftp beamer script".
> What happens when I build the project is this:
> 
> 1. The C files are compiled to .o (that should be so).
> 2. The beamer script is called with the .o files instead of first building
> the .exe and then calling the script.
> 
> So it seems to me that
> a) I am making a mistake or
> b) the current MBS system cannot figure out that it has to make a three-
> stage build process.
> 
> I am aware that the planned features for CDT 3.0 include support for
> "custom build steps". So here are my questions:
> 
> - Am I doing something wrong? Can anybody help me?
> - Is there another workaround for what I am planning to do?
> - Or should I just wait for CDT 3.0?
> 
> Thanks for your advice!
> 
> 
> Norbert Plött
> 
> =======================
> Dr.-Ing. Norbert Plött
> Siemens A&D ATS 1
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cdt-dev
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cdt-dev