Updates: Status: Accepted
Comment #11 on issue 66 by camillob...@gmail.com: CMake should set up to use gcc in Lion http://code.google.com/p/cog/issues/detail?id=66
It does not make sense to hardcode gcc in the CMake config. You can simply set a ENV var (as mentioned in HOWTOBUILD).
Now the build fails under 10.8 since there is no more gcc-4.2. Removing the hardcoded link makes the build succeed
Comment #12 on issue 66 by esteba...@gmail.com: CMake should set up to use gcc in Lion http://code.google.com/p/cog/issues/detail?id=66
that's old... I'm compiling with llvm without problems (since the stack overflow fix).
Comment #13 on issue 66 by sean.p.d...@gmail.com: CMake should set up to use gcc in Lion http://code.google.com/p/cog/issues/detail?id=66
@esteban: does the VM compile in 10.8 (Mountain Lion)? I want to upgrade, but need to still be able to compile the VM...
Comment #14 on issue 66 by camillob...@gmail.com: CMake should set up to use gcc in Lion http://code.google.com/p/cog/issues/detail?id=66
I still see a gcc path hardcoded when I download the latest vmmaker image: CogFamilyCococaIOSConfig >>#setGlobalOptions:
and they still persist in the latest sources from VMMaker. maker set: 'CMAKE_C_COMPILER' to: '/usr/bin/gcc'. maker set: 'CMAKE_CXX_COMPILER' to: '/usr/bin/g++'.
why would you hardcode this? you can simply do an export CC='/foo/bar/myGCC' and everything is perfectly flexible...
Comment #15 on issue 66 by esteba...@gmail.com: CMake should set up to use gcc in Lion http://code.google.com/p/cog/issues/detail?id=66
the vm compiles with 10.8 and llvm out of the box (with latests cmakemaker versions)... the global sets shouldn't be a problem unless you forgot to install Command Line Tools :)
Comment #16 on issue 66 by camillob...@gmail.com: CMake should set up to use gcc in Lion http://code.google.com/p/cog/issues/detail?id=66
ok but then I cannot compile under 10.8 with the vm maker image provided on Jenkins... But then again, it does not make any sense to hardcode the compilers in the VMMaker files, that is what you have the $CC env variable for..
Comment #17 on issue 66 by esteba...@gmail.com: CMake should set up to use gcc in Lion http://code.google.com/p/cog/issues/detail?id=66
yes you can I can you can everybody can
if you install command line tools (from xcode) :)
Comment #18 on issue 66 by camillob...@gmail.com: CMake should set up to use gcc in Lion http://code.google.com/p/cog/issues/detail?id=66
Not with the image from Jenkins. Also not with the image generator script in the gitorious repos. Yes with the latest packages in VMMaker.
Comment #19 on issue 66 by siguc...@gmail.com: CMake should set up to use gcc in Lion http://code.google.com/p/cog/issues/detail?id=66
Guys, your problem is that you want to make a single configuration work everywhere. A configs serve to be working on a specific platform / version , and hardcoding is on purpose, that you specify settings for specific platform/environment. If you change system/environment, it will not work anymore, and to adapt config for other system, you either make a subclass, or fresh new class, where you again hardcode everything. I prefer to have multiple classes per each platform/version than a single one with lots of IFs and case statements, because at some point you getting lost in them and no longer can understand why it fails.
Comment #20 on issue 66 by camillob...@gmail.com: CMake should set up to use gcc in Lion http://code.google.com/p/cog/issues/detail?id=66
I repeat: - the configuration should simply not hardcode the path to the compilers - you set the compiler in your bash environment if you want to override it: export CC=/path/to/my/gcc
that works on all OSXes. So this has nothing to do with the specific platform, its simply a mistake in the configuration... But right now you overwrite a feature of cmake which does not make sense to be overridden!
vm-dev@lists.squeakfoundation.org
-
cog＠googlecode.com