HOWTO: Have command line build copy *.o's to Build Spec dir like Tornado build? - VxWorks

This is a discussion on HOWTO: Have command line build copy *.o's to Build Spec dir like Tornado build? - VxWorks ; When i build in Tornado it copies all the *.o's and *.out's to a Build Spec directory (i.e SIMNTgnu). When i build from the command line it leaves the *.o's and *.out's in the same directory as the source. How ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: HOWTO: Have command line build copy *.o's to Build Spec dir like Tornado build?

  1. HOWTO: Have command line build copy *.o's to Build Spec dir like Tornado build?

    When i build in Tornado it copies all the *.o's and *.out's to a Build
    Spec directory (i.e SIMNTgnu). When i build from the command line it
    leaves the *.o's and *.out's in the same directory as the source. How
    do i get the *.o's and *.out's to be copied to the Build Spec directory
    when compiling from the command line and when compiling from Tornado.

    The reason for this is i'm trying to make a release script that builds
    multiple projects and creates a directory ready to be used by a target
    with all required *.out's. But I don't want to confuse the developers
    using Tornado.

    Thanks,
    George


  2. Re: HOWTO: Have command line build copy *.o's to Build Spec dir like Tornado build?

    On 13 Mar 2006, george.camann@gmail.com wrote:
    > When i build in Tornado it copies all the *.o's and *.out's to a
    > Build Spec directory (i.e SIMNTgnu). When i build from the command
    > line it leaves the *.o's and *.out's in the same directory as the
    > source. How do i get the *.o's and *.out's to be copied to the Build
    > Spec directory when compiling from the command line and when
    > compiling from Tornado.


    I think that you go to the "Build Spec" directory and use the command
    "make -f ../Makefile" (you need some BUILD_SPEC=PPCgnuvx, or something
    too). This should place the object files where you would like them.

    There is a WindSurf technote (appnote, WTN, etc.) on this subject. I
    believe there is also something in the vxFAQ [see below]. There is
    also a .tcl file somewhere in the Tornado distribution for this. One
    thing you might not want to do is check in the Makefiles; only the
    project files. The makefiles can be generated by calling some TCL
    functions. I think this can keep path information out of your
    revision control system if you do this... It also stopped developers
    from committing "out of sync" Makefiles to CVS, etc.

    Ie, a developer enables "debug" locally via the project. The
    developer builds and then reverts the project file. Then commits all
    changes in the directory. This was a problem before removing the
    Makefile from CVS. The build co-ordinator is the only person who
    usually needed the makefile. Most developers liked the project files.
    Only a few odd balls like me preferred the text makefiles...

    Of course your organizations develop habits/policy would dictate this.

    hth,
    Bill Pringlemeir.

    --
    Keep things as simple as possible, but no simpler. - A. Einstein

    vxWorks FAQ, "http://www.xs4all.nl/~borkhuis/vxworks/vxworks.html"

  3. Re: HOWTO: Have command line build copy *.o's to Build Spec dir like Tornado build?

    Perfect, thanks, and great tip about using "makeGen.bat" to create
    Makefile.


+ Reply to Thread