gasranfc.blogg.se

Mingw or cygwin
Mingw or cygwin











mingw or cygwin mingw or cygwin
  1. #Mingw or cygwin install
  2. #Mingw or cygwin windows

When people try out Chicken, I want to be able to ask "normal Windows" environments completely separate from each Notīecause I love Unix, but because I want to keep my MSYS and

#Mingw or cygwin windows

Thing" for people who are using Windows as a Unix-alike. And so, I would like to detect MSYS and "do the right It's really MSYS that's the dependency here,

#Mingw or cygwin install

MinGW sans MSYS, and install things to "C:/Program Files" in the However, the wrinkle is it's also perfectly legitimate to use System, so a proper prefix would more likely be "/usr/local". However, this doesn't actually make sense to a I notice that on Windows the default CMAKE_INSTALL_PREFIX is "C:/ Suppose the above could be abstracted to ANYPROJECT_INSTALL_PREFIX with It may increase the odds of the problemīeing ironed out, and also elevate Chicken people's CMake skills. Good trick, although stylistically I prefer the PreLoad.cmake version Prefix to /usr/local if you pick "Unix Makefiles" from a CMakeSetup run from msys. I tested the above, and it sets the install It will hide the cmake variable CMAKE_INSTALL_PREFIXĪnd make it always the same as CHICKEN_INSTALL_PREFIX. This is a common way of overriding a cmake variable. SET(CHICKEN_INSTALL_PREFIX $ CACHE INTERNAL "") SET(CHICKEN_INSTALL_PREFIX "/usr/local" CACHE PATH "Mingw default install path") I just looked at what was in the environment and figured, heh, this looks like it'll work.Īnther way to do this until the bug is fixed is just to add the following into the chicken cmakelist file: If it doesn't, I'm thinking it should, because MinGW and MSYS are like bread and butter, even if bread can be eaten without butter. I am wondering if CMake has its own, native, more reliable way of doing this. My understanding is that this command must be in PreLoad.cmake, that it cannot just be in CMakeLists.txt, as it must be set before anything else happens. Gleaning knowledge from the archives, I have created a PreLoad.cmake which successfully detects MSYS. This is a bug, for MINGW, it should not be "C:/Program Files". When people try out Chicken, I want to be able to ask "are you using the MinGW, the Cygwin, or the VC++ build?" and not have there be any confusion about what got installed where. Not because I love Unix, but because I want to keep my MSYS and "normal Windows" environments completely separate from each other. And so, I would like to detect MSYS and "do the right thing" for people who are using Windows as a Unix-alike. It's really MSYS that's the dependency here, not MinGW. However, the wrinkle is it's also perfectly legitimate to use MinGW sans MSYS, and install things to "C:/Program Files" in the normal Windows way. MSYS implements a unix-style file system, so a proper prefix would more likely be "/usr/local". However, this doesn't actually make sense to a MinGW user employing MSYS. I notice that on Windows the default CMAKE_INSTALL_PREFIX is "C:/Program Files". I have read the archives quite a bit and I think it's time to ask the question. Hi, I'm going up the CMake Windows learning curve on behalf of Chicken Scheme. "The pioneer is the one with the arrows in his back." I just looked at what was in the environment and figured, heh, this I am also wondering if anyone knows if OSTYPE is a reliable indicator. Like bread and butter, even if bread can be eaten without butter. If it doesn't, I'm thinking it should, because MinGW and MSYS are I am wondering if CMake has its own, native, more reliable way of doing SET(CMAKE_INSTALL_PREFIX "/usr/local" CACHE PATH It must be set before anything else happens. Must be in PreLoad.cmake, that it cannot just be in CMakeLists.txt, as Gleaning knowledge from the archives, I have created a PreLoad.cmake :-) Aside from being highlyīiased towards MinGW support issues, it happens that Eclipse gets messed Wishing to try this out if I can avoid it. Seemed to indicate that it may use /usr/local by default. Try out Chicken, I want to be able to ask "are you using the MinGW, theĬygwin, or the VC++ build?" and not have there be any confusion aboutĭoes a similar issue pertain to Cygwin? Maybe not, as the archives Windows" environments completely separate from each other. Not because I love Unix, but because I want to keep my MSYS and "normal "do the right thing" for people who are using Windows as a Unix-alike. "C:/Program Files" in the normal Windows way. However, the wrinkle is it'sĪlso perfectly legitimate to use MinGW sans MSYS, and install things to Prefix would more likely be "/usr/local". MSYS implements a unix-style file system, so a proper However, this doesn't actually make sense to a MinGW userĮmploying MSYS. I notice that on Windows the default CMAKE_INSTALL_PREFIX is "C:/Programįiles". I have read the archives quite a bit and I think it's time to ask the Hi, I'm going up the CMake Windows learning curve on behalf of Chicken













Mingw or cygwin