[Vm-dev] build.macos*/third-party
Ben Coman
btc at openinworld.com
Sat Oct 29 02:32:22 UTC 2016
+1, seems obvious, and no obvious detractions.
cheers -ben
On Sat, Oct 29, 2016 at 7:19 AM, Eliot Miranda <eliot.miranda at gmail.com> wrote:
>
> Hi Esteban, Hi volunteers,
>
> I somewhat like this structure:
>
> build.macos32x86/third-party:
> cairo libgit2 libsdl2 openssl pkgconfig
> freetype2 libpng libssh2 pixman
>
> build.macos64x64/third-party:
> cairo libgit2 libsdl2 openssl pkgconfig
> freetype2 libpng libssh2 pixman
>
> What's wrong currently is that e.g. build.macos*/pharo.cog.spur builds each library in its build subdirectories (build.macos*/pharo.cog.spur/{build,buildast,building}/third-party) and so there is duplication.
>
> Instead can we not organise it this way: Add build, buildast and builddbg directories to each of the third-party directories and cd there to do the builds? That way we build each library once only per production,assert or debug build, and not once per specific build. This way we can share e.g. the openssl library built from build.macos*/third-party/openssl between all of the builds (stack & cog x pharo,squeak,newspeak), which is 6 times less build effort.
>
> _,,,^..^,,,_
> best, Eliot
>
More information about the Vm-dev
mailing list