[ECOS] Addition: [ECOS] ecos build system remarks (configtool/ecosconfig)

[ECOS] Addition: [ECOS] ecos build system remarks (configtool/ecosconfig)

[Peter Soetens]

I forgot another very important one :

* the headers are copied to the install directory (again build.cxx), why not 
make symbolic links (to be optional) ? If my IDE opens a header for fixing 
compile errors, it will always open the installed version, thus modifying not 
the original.
-> This only requires a trivial patch.
 
Even more, looking at how headers are installed in 'makefile', this could even 
be put in a rules.mak file instead of outputing all the separate targets... 
but that connects again with my first point in the previous mail.

Peter

On Thursday 11 September 2003 11:11, Peter Soetens wrote:
> Hi,
>
> After using the build system a couple of weeks, I have the following
> remarks/questions :
>
> * Shouldn't extension recognition be extended beyond .c,.h,.cxx,.hxx ?
>       (and at which places must this be done ?)
> * What is the 'good practice rule' for putting something in the rules.mak
> file or putting it in the build.cxx file ?
> * ar -rcs is slow with large archive, better do first ar -rc and ranlib at
> the end. This is however hardcoded in common/common/build.cxx
> * make clean should remove the libtarget.a file (or make a new target which
>      does so)
> * the make property has obligatory dependencies. I'd like to have a make
>      rule that is executed at each make, unconditionaly, so without
>      dependencies.
> * How would you specify a dependency on libtarget.a itself in a custom make
>     property ?
>
> I am aware of your TODO list, but these are my personal priorities :-)
> Which of them are likely to be accepted if a patch is submitted ?
>
> Peter
>
> --
> ------------------------------------------------------------------------
> Peter Soetens                                      http://www.orocos.org
> Katholieke Universiteit Leuven
> Division Production Engineering,                      tel. +32 16 322773
> Machine Design and Automation                         fax. +32 16 322987
> Celestijnenlaan 300B                   peter.soetens@mech.kuleuven.ac.be
> B-3001 Leuven Belgium                 http://www.mech.kuleuven.ac.be/pma
> ------------------------------------------------------------------------

-- 
------------------------------------------------------------------------
Peter Soetens                                      http://www.orocos.org
Katholieke Universiteit Leuven
Division Production Engineering,                      tel. +32 16 322773
Machine Design and Automation                         fax. +32 16 322987
Celestijnenlaan 300B                   peter.soetens@mech.kuleuven.ac.be
B-3001 Leuven Belgium                 http://www.mech.kuleuven.ac.be/pma
------------------------------------------------------------------------


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

[ECOS] ecos build system remarks (configtool/ecosconfig)

[Peter Soetens]

Hi,

After using the build system a couple of weeks, I have the following 
remarks/questions :

* Shouldn't extension recognition be extended beyond .c,.h,.cxx,.hxx ?
      (and at which places must this be done ?)
* What is the 'good practice rule' for putting something in the rules.mak file
      or putting it in the build.cxx file ?
* ar -rcs is slow with large archive, better do first ar -rc and ranlib at the
      end. This is however hardcoded in common/common/build.cxx
* make clean should remove the libtarget.a file (or make a new target which
     does so)
* the make property has obligatory dependencies. I'd like to have a make
     rule that is executed at each make, unconditionaly, so without
     dependencies.
* How would you specify a dependency on libtarget.a itself in a custom make
    property ?

I am aware of your TODO list, but these are my personal priorities :-)
Which of them are likely to be accepted if a patch is submitted ?

Peter

-- 
------------------------------------------------------------------------
Peter Soetens                                      http://www.orocos.org
Katholieke Universiteit Leuven
Division Production Engineering,                      tel. +32 16 322773
Machine Design and Automation                         fax. +32 16 322987
Celestijnenlaan 300B                   peter.soetens@mech.kuleuven.ac.be
B-3001 Leuven Belgium                 http://www.mech.kuleuven.ac.be/pma
------------------------------------------------------------------------


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

Re: [ECOS] ecos build system remarks (configtool/ecosconfig)

[Andrew Lunn]

On Thu, Sep 11, 2003 at 11:11:22AM +0200, Peter Soetens wrote:
> Hi,
> 
> After using the build system a couple of weeks, I have the following 
> remarks/questions :
> 
> * Shouldn't extension recognition be extended beyond .c,.h,.cxx,.hxx ?
>       (and at which places must this be done ?)

Well, this covers everything thats currently in the sources as far as
im aware. Do you have a package written in Fortran, Ada, or some other
language....

> * ar -rcs is slow with large archive, better do first ar -rc and ranlib at 
    the end. 

Actually, i don't think this works. Once you have run ranlib once, ar
will always maintain the index unless -q is added. But we cannot use
-q because we need to replace existing objects in the archives with
new ones when we do a rebuild. Also, if you read the man page of gnu
ar, it says -q does not in fact do a quick append but a replace! 

    Andrew

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

Re: [ECOS] Addition: [ECOS] ecos build system remarks (configtool/ecosconfig)

[Andrew Lunn]

On Thu, Sep 11, 2003 at 11:23:44AM +0200, Peter Soetens wrote:
> 
> I forgot another very important one :
> 
> * the headers are copied to the install directory (again build.cxx), why not 
> make symbolic links (to be optional) ? If my IDE opens a header for fixing 
> compile errors, it will always open the installed version, thus modifying not 
> the original.

The install directory is designed to be stand alone. You have
everything you need within it to build eCos applications. You don't
need the repository any more. You can ship the install directory to
customers, mirror it to other development machines, archive it to tape
etc, knowing its stand alone.

If you had symbolic links, a cvs up of your repository could
potentially break your working work-trees.

O yes, symbol links are also not particularly well supported on M$
systems.

After falling into the IDE trap a few times, you learn the lesson. One
thing to try. Does you IDE know about symbolic links? When you edit a
symbolic link file, does it change the linked file, or replace the
symbolic link we a new copy of the file? Most editors tend to play
safe by creating a new tmp file with the new contents, rename the old
file to .bak and then rename the tmp to the source file name. This
obviously doesn't work with symbolic links.....

For me, the current way of doing it is correct.

          Andrew

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

Re: [ECOS] ecos build system remarks (configtool/ecosconfig)

[Peter Soetens]

On Thursday 11 September 2003 11:38, Andrew Lunn wrote:
> On Thu, Sep 11, 2003 at 11:11:22AM +0200, Peter Soetens wrote:
> > Hi,
> >
> > After using the build system a couple of weeks, I have the following
> > remarks/questions :
> >
> > * Shouldn't extension recognition be extended beyond .c,.h,.cxx,.hxx ?
> >       (and at which places must this be done ?)
>
> Well, this covers everything thats currently in the sources as far as
> im aware. Do you have a package written in Fortran, Ada, or some other
> language....

What about external packages using the .cc / .C / .cpp and so... on 
extensions?

>
> > * ar -rcs is slow with large archive, better do first ar -rc and ranlib
> > at
>
>     the end.
>
> Actually, i don't think this works. Once you have run ranlib once, ar
> will always maintain the index unless -q is added. But we cannot use
> -q because we need to replace existing objects in the archives with
> new ones when we do a rebuild. Also, if you read the man page of gnu
> ar, it says -q does not in fact do a quick append but a replace!

Correct, but you should supress index building with 'S' and not -q. So :
ar rcS <.a file> <.o files>
ranlib <.a file>

Peter

-- 
------------------------------------------------------------------------
Peter Soetens                                      http://www.orocos.org
Katholieke Universiteit Leuven
Division Production Engineering,                      tel. +32 16 322773
Machine Design and Automation                         fax. +32 16 322987
Celestijnenlaan 300B                   peter.soetens@mech.kuleuven.ac.be
B-3001 Leuven Belgium                 http://www.mech.kuleuven.ac.be/pma
------------------------------------------------------------------------


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss