On 05/05/2010 04:00 PM, Philip Lowman wrote:
> Usually you can get away with deleting just the cached variables that a find
> module create (i.e. ZLIB_LIBRARY, etc.). Boost is one of the few modules
> where this doesn't always work because it creates internal cached variables
> that don't show up
Usually you can get away with deleting just the cached variables that a find
module create (i.e. ZLIB_LIBRARY, etc.). Boost is one of the few modules
where this doesn't always work because it creates internal cached variables
that don't show up in the cache editor.
On Wed, May 5, 2010 at 9:57 AM,
On 05/04/2010 07:19 PM, Mike Ladwig wrote:
> The "clean build tree" seems to have been the problem. Looks as if I needed
> to start clean every time I tried a new configuration approach. Much
> thanks!
Typically, if FIND_PACKAGE() succeeds in locating a package the results
are cached, and if you
The "clean build tree" seems to have been the problem. Looks as if I needed
to start clean every time I tried a new configuration approach. Much
thanks!
On Tue, May 4, 2010 at 1:01 PM, S Roderick wrote:
> On May 4, 2010, at 12:41 , Mike Ladwig wrote:
>
> > Hi.
> >
> > I'm having a problem comp
On May 4, 2010, at 12:41 , Mike Ladwig wrote:
> Hi.
>
> I'm having a problem compiling scantailor on CentOS 5.4. The version of
> cmake that comes with CentOS was too old, so I downloaded the current cmake
> binary, which seems to be working well.
>
> The problem is that the CentOS version of
Hi.
I'm having a problem compiling scantailor on CentOS 5.4. The version of
cmake that comes with CentOS was too old, so I downloaded the current cmake
binary, which seems to be working well.
The problem is that the CentOS version of boost is also out-of-date, so I
needed to download and build t
