Hi all,
Sorry to bore you with this kind of stuff :-)
I just would like to ask every developers involved in Étoilé to pay
more attention to keep trunk in a buildable state as much as possible.
To help you in this task, I'm just going to make a short summary of
some important points…
When you remove/rename a module in trunk, don't forget to update the
related GNUmakefile in the parent directory. It's also valid if you
want to include a module in the build process.
Here is an example of what you have to do: <http://svn.gna.org/
viewcvs/etoile?rev=1487&view=rev>
Use trunk/Etoile/ChangeLog to mention updates (like the previous one)
not related to a specific module.
Don't forget to include etoile.make in your module GNUmakefile when
you commit a new module for the first time.
Take note the whole repository could compile on your machine but not
on another one, most of the time because you have a full or partial
Etoile install on your machine. This means dependencies will be
resolved on your machine. Therefore when you move or add a module you
should take time to remove installed frameworks on your machine to
check whether they are properly found in trunk/Etoile/Build at
compilation time. Any library/framework that includes etoile.make has
its header and its library file exported in Build directory.
As a general guideline, check the compilation by just typing 'make'
in /trunk/Etoile/… Just do it all the time if you have a fast machine
and you feel brave ;-)
General development guidelines about the project are summarized here:
<http://svn.gna.org/viewcvs/etoile/trunk/Etoile/HACKING>
I would like to set up a machine to run daily or hourly builds since
the inner dependencies are already numerous/complicated and this will
get worse as time goes by. If anybody want or can help to set up
such test machine, let me know :-)
Cheers,
Quentin.
--
Quentin Mathé
[EMAIL PROTECTED]
_______________________________________________
Etoile-dev mailing list
[email protected]
https://mail.gna.org/listinfo/etoile-dev
