"Manuel A. Fernandez Montecelo" writes:
> 2012/11/21 Manuel A. Fernandez Montecelo <manuel.montez...@gmail.com>:
>> Lastly, I couldn't build it in a beefier machine today at work, but
>> I'm trying again now, will tell the result later.
> Failed to build again, it looks like ~7GB isn't enough... will have to
> make more room to compile or try to grab the beefier machine soon.
Yes, looking at the build tree it says
$ du -sm
Nevertheless, I am starting to be worried about the size of the overall
project. I don't know if it is really worth to have the static version
of the library. It doubles build times and space requirements.
Furthermore, it is typically aimed at developers, and popcon results
show that OSG is mainly used as a dependency for other projects and not
for developing. If at least the static build were complex, its
usefulness could be proven, but experience tells me that usually
developers are compiling their own versions from the SVN upstream
I had an idea of making a separate package for the static libraries in
order to have popcon results saying what it real impact is, but now I
just think that we could skip the burden of asking for permission to the
ftp masters in order to create a new package and just not build them.
Therefore debian/rules could be as small and lean as those other project
of yours, pruning all that casuistic code that plagues the current
Pkg-osg-devel mailing list