Hi Alex,
Sorry about forgetting to CC the list last time. You're right: it was the
CXX_FLAGS vs C_FLAGS problem. I have so many things to think about that I
don't even realize which language is being compiled :-)
Jerry
2011/7/7 Alexander Neundorf
> Hi,
>
> On Wednesday 06 July 2011, Jerry Gage
Hi,
On Wednesday 06 July 2011, Jerry Gagelman wrote:
> Thanks, Alex. That was my bad. I also realized that the CXX_FLAGS were
> (correctly) getting passed to the compiler. Changing CMakeLists.txt
> accordingly does fix the last problem that I reported.
I'm happy that I could help you.
So the prob
May be you're looking for overriding default flags?
http://www.cmake.org/Wiki/CMake_FAQ#Make_Override_Files
Although it mentions VS static runtime, this approach is very useful to set
own initial flags in CMake.
On Wed, Jul 6, 2011 at 5:41 PM, Jerry Gagelman wrote:
> I'm redistributing a library
On Wednesday 06 July 2011, Jerry Gagelman wrote:
> 2011/7/6 Alexander Neundorf
>
> > On Wednesday 06 July 2011, Jerry Gagelman wrote:
> >
> > If these variables exist already in the cache, then a simple
> > set(... CACHE ...)
> > does not override the value which is already in the cache.
> > You
On 07/06/2011 03:41 PM, Jerry Gagelman wrote:
> I'm redistributing a library for which the original authors have hand coded
> their own Makefile, but I would like to streamline everything with CMake.
> Their Makefile provides for Debug and Release flavored configurations, each
> has its own set of
2011/7/6 Alexander Neundorf
> On Wednesday 06 July 2011, Jerry Gagelman wrote:
>
> If these variables exist already in the cache, then a simple
> set(... CACHE ...)
> does not override the value which is already in the cache.
> You can only override a value in the cache from a CMakeLists.txt by u
On Wednesday 06 July 2011, Jerry Gagelman wrote:
> I'm redistributing a library for which the original authors have hand coded
> their own Makefile, but I would like to streamline everything with CMake.
> Their Makefile provides for Debug and Release flavored configurations, each
> has its own set
I'm redistributing a library for which the original authors have hand coded
their own Makefile, but I would like to streamline everything with CMake.
Their Makefile provides for Debug and Release flavored configurations, each
has its own set of CFLAGS, and for consistency I would like to incorporat
