Hi Allen,
Allen Bierbaum wrote:
>
> I can put my finger on it for sure, the current setup just has a bad
> smell to it. There are duplicated settings in many places. Maybe it
> really points to the code being separated in multiple places and the
> source tree needs reorganized... I don't really know. In any case the
> current setup is a pain when problems like this crop up because there is
> no place you can go to see the "standard" dependencies for a given
> library. You have to look in multiple build.info files throughout the
> tree.
>
> The current setup would not be bad if there was one single place
> (directory) that could be considered the "standard" root for a given
> library. Then we could put all the lib deps in there and not replicate
> them everywhere else. In other directories the build.info file would
> end up very simple and only really saying what library to put the code
> into.
That sounds like a good idea. I don't think this should be an issue, as
all the build.info files do is add stuff to existing variables/maps, so
as long as one place adds the right stuff we should be fine, right?
> I would not want to give up the current support, I am just looking for a
> way to centralize the basics of it a little more.
Dirk
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
