[sldev] cmake weirdness

[Soft]

On Tue, Jul 8, 2008 at 4:07 PM, Jason Giglio <gigstaggart at gmail.com> wrote:
>
>> The new cmake setup pulls individual library bundles as needed - we're
>> phasing out the single giant library tarballs. The cmake scripts cache
>> these locally so that as libraries are updated or as you switch
>> between branches, only the libs that you're using for the first time
>> will need to be downloaded.
>
> So this means it will be impossible to make a portable build with cmake
> from here on out, because it'll assume you have the system level
> libraries of the system you built it on?

I'm not clear on where you see that.

The new system pulls the same libraries that were previously in the
monolithic library bundles. It shouldn't ever select system-provided
libraries in cases where it didn't previously - it still downloads
these. Fundamentally, this is designed as an alternative delivery
mechanism to stop you from having to download the giant library bundle
repeatedly when only one library has actually changed. That should be
all it affects - any other change should be filed as a bug in JIRA or
brought up here. Hopefully we can make it more clear and friendly
before 1.21 forks off of release/.

I apologize for this hitting release/ without a preview branch for us
to iterate over the changes and get them more polished. This should
have been handled more like the first wave of cmake changes.
Unfortunately, this was one of those cases where the right hand didn't
know what the left was doing.