Re: [Qgis-developer] Time to retire OS X Xcode project
+1 to change the qwt build instructions to better conform with other systems. On Nov 11, 2010, at 11:12 AM, William Kyngesburye wrote: > ... ah, the cmake check tests /usr/local/lib, but the qwt build uses an > isolated versioned subfolder. It's not just the local copy in the pyqwt > source, but the way the main qwt source is distributed, so the qwt detection > needs some tweaking, though that could get messy. Or I could change the Mac > instructions to remove the versioned subfolder from the qwt install location > (probably matches better how binaries in linux distros are done). > > On Nov 11, 2010, at 12:53 PM, John C. Tull wrote: > >> Hi William, >> >> I am trying to follow your instructions and new cmake build procedure. Upon >> running the basic cmake command: >> cmake -D CMAKE_INSTALL_PREFIX=~/Applications -D CMAKE_BUILD_TYPE=Release \ >> -D CMAKE_BUILD_TYPE=MinSizeRel -D WITH_INTERNAL_SPATIALITE=FALSE \ >> .. >> >> I run into an error in finding qwt: >> CMake Error at cmake/FindQWT.cmake:41 (MESSAGE): >> Could not find QWT >> Call Stack (most recent call first): >> CMakeLists.txt:143 (FIND_PACKAGE) >> >> I had to add the paths to qwt lib and include with the appropriate flags or >> using ccmake. >> >> Thanks, >> John >> >> On Nov 10, 2010, at 1:17 PM, William Kyngesburye wrote: >> >>> It's all pretty much done now in SVN, and should be in the 1.6 release. >>> See the INSTALL document in SVN for build details. For Qwt, I have the >>> install_name_tool step there. All that's left is the final bundling step >>> for the standalone, but that will have to wait for a gdaltools issue. >>> >>> On Nov 10, 2010, at 2:52 PM, John C. Tull wrote: >>> I've not been monitoring the list lately. Feel free to contact me offline if you want to compare notes on cmake builds, although you are probably all caught up with my level of knowledge already. FWIW, this is the cmake command I run when building with your frameworks. cmake -D BINDINGS_GLOBAL_INSTALL=on\ -D QWT_INCLUDE_DIR=/usr/local/qwt-5.2.1-svn/include\ -D QWT_LIBRARY=/usr/local/qwt-5.2.1-svn/lib/libqwt.5.dylib\ -D CMAKE_INSTALL_PREFIX=/Applications\ -D CMAKE_BUILD_TYPE=Release -D SIP_BINARY_PATH=/usr/local/bin/sip\ -D CMAKE_OSX_ARCHITECTURES=x86_64\ -D GRASS_PREFIX=/Applications/GRASS-6.4.app/Contents/MacOS\ -D GRASS_INCLUDE_DIR=/Applications/GRASS-6.4.app/Contents/MacOS/include .. You may have run into the quirky issues with qwt by now. That, of course, is not a qgis issue but qwt. I still have not managed to build qwt in a manner that does not require the install_name_tool command. I'm glad to know you will be continuing to help out with qgis. I started to panic when I first started reading your email. Regards, John On Oct 28, 2010, at 3:57 PM, William Kyngesburye wrote: > It's been a bit (lot?) of work maintaining sync with the cmake build. > Other problems with it (both new and from day 1): > > >>> > > Not to fear! I've taken the plunge into cmake and have been working on a > cmake overhaul for the OS X build. I was going to wait for after the > sudden 1.6 release, but since I'm not having luck with yacc/lex in Xcode > I should have at least the core changes done for 1.6 (up to bundling Qt > frameworks is done now, but not in SVN yet). > > Part of the cmake overhaul is to make sure library linking is all fixed > up (it's been a problem in the past). Another improvement is cleaner > (and automatic) detection of my frameworks (needed for bundling to work). > The main improvement is making the bundling steps part of the install. > >>> >>> - >>> William Kyngesburye >>> http://www.kyngchaos.com/ >>> >>> "I ache, therefore I am. Or in my case - I am, therefore I ache." >>> >>> - Marvin >>> >>> >> >> ___ >> Qgis-developer mailing list >> Qgis-developer@lists.osgeo.org >> http://lists.osgeo.org/mailman/listinfo/qgis-developer > > - > William Kyngesburye > http://www.kyngchaos.com/ > > "Oh, look, I seem to have fallen down a deep, dark hole. Now what does that > remind me of? Ah, yes - life." > > - Marvin > > ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Time to retire OS X Xcode project
... ah, the cmake check tests /usr/local/lib, but the qwt build uses an isolated versioned subfolder. It's not just the local copy in the pyqwt source, but the way the main qwt source is distributed, so the qwt detection needs some tweaking, though that could get messy. Or I could change the Mac instructions to remove the versioned subfolder from the qwt install location (probably matches better how binaries in linux distros are done). On Nov 11, 2010, at 12:53 PM, John C. Tull wrote: > Hi William, > > I am trying to follow your instructions and new cmake build procedure. Upon > running the basic cmake command: > cmake -D CMAKE_INSTALL_PREFIX=~/Applications -D CMAKE_BUILD_TYPE=Release \ > -D CMAKE_BUILD_TYPE=MinSizeRel -D WITH_INTERNAL_SPATIALITE=FALSE \ > .. > > I run into an error in finding qwt: > CMake Error at cmake/FindQWT.cmake:41 (MESSAGE): > Could not find QWT > Call Stack (most recent call first): > CMakeLists.txt:143 (FIND_PACKAGE) > > I had to add the paths to qwt lib and include with the appropriate flags or > using ccmake. > > Thanks, > John > > On Nov 10, 2010, at 1:17 PM, William Kyngesburye wrote: > >> It's all pretty much done now in SVN, and should be in the 1.6 release. See >> the INSTALL document in SVN for build details. For Qwt, I have the >> install_name_tool step there. All that's left is the final bundling step >> for the standalone, but that will have to wait for a gdaltools issue. >> >> On Nov 10, 2010, at 2:52 PM, John C. Tull wrote: >> >>> I've not been monitoring the list lately. Feel free to contact me offline >>> if you want to compare notes on cmake builds, although you are probably all >>> caught up with my level of knowledge already. FWIW, this is the cmake >>> command I run when building with your frameworks. >>> >>> cmake -D BINDINGS_GLOBAL_INSTALL=on\ >>> -D QWT_INCLUDE_DIR=/usr/local/qwt-5.2.1-svn/include\ >>> -D QWT_LIBRARY=/usr/local/qwt-5.2.1-svn/lib/libqwt.5.dylib\ >>> -D CMAKE_INSTALL_PREFIX=/Applications\ >>> -D CMAKE_BUILD_TYPE=Release -D SIP_BINARY_PATH=/usr/local/bin/sip\ >>> -D CMAKE_OSX_ARCHITECTURES=x86_64\ >>> -D GRASS_PREFIX=/Applications/GRASS-6.4.app/Contents/MacOS\ >>> -D GRASS_INCLUDE_DIR=/Applications/GRASS-6.4.app/Contents/MacOS/include .. >>> >>> You may have run into the quirky issues with qwt by now. That, of course, >>> is not a qgis issue but qwt. I still have not managed to build qwt in a >>> manner that does not require the install_name_tool command. >>> >>> I'm glad to know you will be continuing to help out with qgis. I started to >>> panic when I first started reading your email. >>> >>> Regards, >>> John >>> >>> On Oct 28, 2010, at 3:57 PM, William Kyngesburye wrote: >>> It's been a bit (lot?) of work maintaining sync with the cmake build. Other problems with it (both new and from day 1): >> Not to fear! I've taken the plunge into cmake and have been working on a cmake overhaul for the OS X build. I was going to wait for after the sudden 1.6 release, but since I'm not having luck with yacc/lex in Xcode I should have at least the core changes done for 1.6 (up to bundling Qt frameworks is done now, but not in SVN yet). Part of the cmake overhaul is to make sure library linking is all fixed up (it's been a problem in the past). Another improvement is cleaner (and automatic) detection of my frameworks (needed for bundling to work). The main improvement is making the bundling steps part of the install. >> >> - >> William Kyngesburye >> http://www.kyngchaos.com/ >> >> "I ache, therefore I am. Or in my case - I am, therefore I ache." >> >> - Marvin >> >> > > ___ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/qgis-developer - William Kyngesburye http://www.kyngchaos.com/ "Oh, look, I seem to have fallen down a deep, dark hole. Now what does that remind me of? Ah, yes - life." - Marvin ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Time to retire OS X Xcode project
Hi William, I am trying to follow your instructions and new cmake build procedure. Upon running the basic cmake command: cmake -D CMAKE_INSTALL_PREFIX=~/Applications -D CMAKE_BUILD_TYPE=Release \ -D CMAKE_BUILD_TYPE=MinSizeRel -D WITH_INTERNAL_SPATIALITE=FALSE \ .. I run into an error in finding qwt: CMake Error at cmake/FindQWT.cmake:41 (MESSAGE): Could not find QWT Call Stack (most recent call first): CMakeLists.txt:143 (FIND_PACKAGE) I had to add the paths to qwt lib and include with the appropriate flags or using ccmake. Thanks, John On Nov 10, 2010, at 1:17 PM, William Kyngesburye wrote: > It's all pretty much done now in SVN, and should be in the 1.6 release. See > the INSTALL document in SVN for build details. For Qwt, I have the > install_name_tool step there. All that's left is the final bundling step for > the standalone, but that will have to wait for a gdaltools issue. > > On Nov 10, 2010, at 2:52 PM, John C. Tull wrote: > >> I've not been monitoring the list lately. Feel free to contact me offline if >> you want to compare notes on cmake builds, although you are probably all >> caught up with my level of knowledge already. FWIW, this is the cmake >> command I run when building with your frameworks. >> >> cmake -D BINDINGS_GLOBAL_INSTALL=on\ >> -D QWT_INCLUDE_DIR=/usr/local/qwt-5.2.1-svn/include\ >> -D QWT_LIBRARY=/usr/local/qwt-5.2.1-svn/lib/libqwt.5.dylib\ >> -D CMAKE_INSTALL_PREFIX=/Applications\ >> -D CMAKE_BUILD_TYPE=Release -D SIP_BINARY_PATH=/usr/local/bin/sip\ >> -D CMAKE_OSX_ARCHITECTURES=x86_64\ >> -D GRASS_PREFIX=/Applications/GRASS-6.4.app/Contents/MacOS\ >> -D GRASS_INCLUDE_DIR=/Applications/GRASS-6.4.app/Contents/MacOS/include .. >> >> You may have run into the quirky issues with qwt by now. That, of course, is >> not a qgis issue but qwt. I still have not managed to build qwt in a manner >> that does not require the install_name_tool command. >> >> I'm glad to know you will be continuing to help out with qgis. I started to >> panic when I first started reading your email. >> >> Regards, >> John >> >> On Oct 28, 2010, at 3:57 PM, William Kyngesburye wrote: >> >>> It's been a bit (lot?) of work maintaining sync with the cmake build. >>> Other problems with it (both new and from day 1): >>> >>> > >>> >>> Not to fear! I've taken the plunge into cmake and have been working on a >>> cmake overhaul for the OS X build. I was going to wait for after the >>> sudden 1.6 release, but since I'm not having luck with yacc/lex in Xcode I >>> should have at least the core changes done for 1.6 (up to bundling Qt >>> frameworks is done now, but not in SVN yet). >>> >>> Part of the cmake overhaul is to make sure library linking is all fixed up >>> (it's been a problem in the past). Another improvement is cleaner (and >>> automatic) detection of my frameworks (needed for bundling to work). The >>> main improvement is making the bundling steps part of the install. >>> > > - > William Kyngesburye > http://www.kyngchaos.com/ > > "I ache, therefore I am. Or in my case - I am, therefore I ache." > > - Marvin > > ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Time to retire OS X Xcode project
It's all pretty much done now in SVN, and should be in the 1.6 release. See the INSTALL document in SVN for build details. For Qwt, I have the install_name_tool step there. All that's left is the final bundling step for the standalone, but that will have to wait for a gdaltools issue. On Nov 10, 2010, at 2:52 PM, John C. Tull wrote: > I've not been monitoring the list lately. Feel free to contact me offline if > you want to compare notes on cmake builds, although you are probably all > caught up with my level of knowledge already. FWIW, this is the cmake command > I run when building with your frameworks. > > cmake -D BINDINGS_GLOBAL_INSTALL=on\ > -D QWT_INCLUDE_DIR=/usr/local/qwt-5.2.1-svn/include\ > -D QWT_LIBRARY=/usr/local/qwt-5.2.1-svn/lib/libqwt.5.dylib\ > -D CMAKE_INSTALL_PREFIX=/Applications\ > -D CMAKE_BUILD_TYPE=Release -D SIP_BINARY_PATH=/usr/local/bin/sip\ > -D CMAKE_OSX_ARCHITECTURES=x86_64\ > -D GRASS_PREFIX=/Applications/GRASS-6.4.app/Contents/MacOS\ > -D GRASS_INCLUDE_DIR=/Applications/GRASS-6.4.app/Contents/MacOS/include .. > > You may have run into the quirky issues with qwt by now. That, of course, is > not a qgis issue but qwt. I still have not managed to build qwt in a manner > that does not require the install_name_tool command. > > I'm glad to know you will be continuing to help out with qgis. I started to > panic when I first started reading your email. > > Regards, > John > > On Oct 28, 2010, at 3:57 PM, William Kyngesburye wrote: > >> It's been a bit (lot?) of work maintaining sync with the cmake build. Other >> problems with it (both new and from day 1): >> >> >> >> Not to fear! I've taken the plunge into cmake and have been working on a >> cmake overhaul for the OS X build. I was going to wait for after the sudden >> 1.6 release, but since I'm not having luck with yacc/lex in Xcode I should >> have at least the core changes done for 1.6 (up to bundling Qt frameworks is >> done now, but not in SVN yet). >> >> Part of the cmake overhaul is to make sure library linking is all fixed up >> (it's been a problem in the past). Another improvement is cleaner (and >> automatic) detection of my frameworks (needed for bundling to work). The >> main improvement is making the bundling steps part of the install. >> - William Kyngesburye http://www.kyngchaos.com/ "I ache, therefore I am. Or in my case - I am, therefore I ache." - Marvin ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Time to retire OS X Xcode project
I've not been monitoring the list lately. Feel free to contact me offline if you want to compare notes on cmake builds, although you are probably all caught up with my level of knowledge already. FWIW, this is the cmake command I run when building with your frameworks. cmake -D BINDINGS_GLOBAL_INSTALL=on\ -D QWT_INCLUDE_DIR=/usr/local/qwt-5.2.1-svn/include\ -D QWT_LIBRARY=/usr/local/qwt-5.2.1-svn/lib/libqwt.5.dylib\ -D CMAKE_INSTALL_PREFIX=/Applications\ -D CMAKE_BUILD_TYPE=Release -D SIP_BINARY_PATH=/usr/local/bin/sip\ -D CMAKE_OSX_ARCHITECTURES=x86_64\ -D GRASS_PREFIX=/Applications/GRASS-6.4.app/Contents/MacOS\ -D GRASS_INCLUDE_DIR=/Applications/GRASS-6.4.app/Contents/MacOS/include .. You may have run into the quirky issues with qwt by now. That, of course, is not a qgis issue but qwt. I still have not managed to build qwt in a manner that does not require the install_name_tool command. I'm glad to know you will be continuing to help out with qgis. I started to panic when I first started reading your email. Regards, John On Oct 28, 2010, at 3:57 PM, William Kyngesburye wrote: > It's been a bit (lot?) of work maintaining sync with the cmake build. Other > problems with it (both new and from day 1): > > - non-user-friendly configuration (hand-edit a file!), though I had an idea > to patch in configuration from cmake > > - no automatic optional target compilation - if you didn't want or didn't > have the support for an optional plugin or feature, you had to build > individual targets > > - the dependency tracking of Xcode never worked right for custom compile > rules (moc, rcc,...) so recompiling a partially-compiled source or after > changes to sources always recompiled those with custom rules, even if they > didn't change > > - the builtin yacc/lex rules don't work right, and custom rules are cranky, > which leads to the final straw today when trying to add a new yacc/lex pair > for the raster calculator change - failure > > > Not to fear! I've taken the plunge into cmake and have been working on a > cmake overhaul for the OS X build. I was going to wait for after the sudden > 1.6 release, but since I'm not having luck with yacc/lex in Xcode I should > have at least the core changes done for 1.6 (up to bundling Qt frameworks is > done now, but not in SVN yet). > > Part of the cmake overhaul is to make sure library linking is all fixed up > (it's been a problem in the past). Another improvement is cleaner (and > automatic) detection of my frameworks (needed for bundling to work). The > main improvement is making the bundling steps part of the install. > > There may be a small delay for my binary packages for the 1.6 release while I > finish the bundling scripts (or I figure out a hack in Xcode for the yacc/lex > problem). > > > Things I will miss from Xcode: > > - debugging in the Xcode GUI, though I haven't needed to set that up so far > > - nothing else really, Xcode/Cmake doesn't matter to me as long as it > compiles QGIS and bundles everything needed for release > > - > William Kyngesburye > http://www.kyngchaos.com/ > > Theory of the Universe > > There is a theory which states that if ever anyone discovers exactly what the > universe is for and why it is here, it will instantly disappear and be > replaced by something even more bizarrely inexplicable. There is another > theory which states that this has already happened. > > -Hitchhiker's Guide to the Galaxy 2nd season intro > > > ___ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Time to retire OS X Xcode project
On Oct 29, 2010, at 4:29 AM, Marco Hugentobler wrote: > Hi William > >> - the builtin yacc/lex rules don't work right, and custom rules are cranky, >> which leads to the final straw today when trying to add a new yacc/lex >> pair for the raster calculator change - failure > > Is this better now with Jürgens fixes to the cmake flex/bison scrips in > r14445? > The problem is in Xcode, which has nothing to do with cmake. - William Kyngesburye http://www.kyngchaos.com/ "I ache, therefore I am. Or in my case - I am, therefore I ache." - Marvin ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Time to retire OS X Xcode project
Hi William > - the builtin yacc/lex rules don't work right, and custom rules are cranky, > which leads to the final straw today when trying to add a new yacc/lex > pair for the raster calculator change - failure Is this better now with Jürgens fixes to the cmake flex/bison scrips in r14445? Marco Am Freitag, 29. Oktober 2010, um 00.57:45 schrieb William Kyngesburye: > It's been a bit (lot?) of work maintaining sync with the cmake build. > Other problems with it (both new and from day 1): > > - non-user-friendly configuration (hand-edit a file!), though I had an idea > to patch in configuration from cmake > > - no automatic optional target compilation - if you didn't want or didn't > have the support for an optional plugin or feature, you had to build > individual targets > > - the dependency tracking of Xcode never worked right for custom compile > rules (moc, rcc,...) so recompiling a partially-compiled source or after > changes to sources always recompiled those with custom rules, even if they > didn't change > > - the builtin yacc/lex rules don't work right, and custom rules are cranky, > which leads to the final straw today when trying to add a new yacc/lex > pair for the raster calculator change - failure > > > Not to fear! I've taken the plunge into cmake and have been working on a > cmake overhaul for the OS X build. I was going to wait for after the > sudden 1.6 release, but since I'm not having luck with yacc/lex in Xcode I > should have at least the core changes done for 1.6 (up to bundling Qt > frameworks is done now, but not in SVN yet). > > Part of the cmake overhaul is to make sure library linking is all fixed up > (it's been a problem in the past). Another improvement is cleaner (and > automatic) detection of my frameworks (needed for bundling to work). The > main improvement is making the bundling steps part of the install. > > There may be a small delay for my binary packages for the 1.6 release while > I finish the bundling scripts (or I figure out a hack in Xcode for the > yacc/lex problem). > > > Things I will miss from Xcode: > > - debugging in the Xcode GUI, though I haven't needed to set that up so far > > - nothing else really, Xcode/Cmake doesn't matter to me as long as it > compiles QGIS and bundles everything needed for release > > - > William Kyngesburye > http://www.kyngchaos.com/ > > Theory of the Universe > > There is a theory which states that if ever anyone discovers exactly what > the universe is for and why it is here, it will instantly disappear and be > replaced by something even more bizarrely inexplicable. There is another > theory which states that this has already happened. > > -Hitchhiker's Guide to the Galaxy 2nd season intro > > > ___ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/qgis-developer -- Dr. Marco Hugentobler Sourcepole - Linux & Open Source Solutions Webereistr. 66, CH-8134 Adliswil, Switzerland marco.hugentob...@sourcepole.ch http://www.sourcepole.ch Technical Advisor QGIS Project Steering Committee ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
