![]() ![]()
There is a history of inconsistent behaviours and it used to be necessary to handle that, but I doubt that still is the case (as suggested in #2546 (comment)). Previously, it was inconsistent in that some platforms/compilers had this flag for the RelWithDebInfo configuration and some didn't. Which simply stands against CMake recommendation of "Do not fiddle with flags, unless you really have to" It is required by policy that CFLAGS and CXXFLAGS (solely) are used when building. #QMAPSHACK BUILD FINDPROJ4.CMAKE PATCH#We should be promoting the use of -DCMAKE_BUILD_TYPE=RelWithDebInfo (-g -O2), and here's a patch that does that. What is the absolute minimum we can do to get around this problem? My goal here is to find an immediate fix we can put into 8.0.0RC2 and hopefully smooth the transition to a proj_api.h-less From that discussion The burden of maintaining to build systems is already too much in my opinion so I would rather not complicate things more than necessary. (Maybe less in the PROJ case, but definitely in the general case.)Īlso resonates with me. Reimplementing CMake config file generation in autotools is going to be a fruitless, volatile maintenance burden. Maybe now is the time to start thinking about that. I generally agree with points, especially the point about dropping autotools but that is my personal opinion and a change like that needs a well thought out strategi and PSC approval. We keep a FindSqlite3.cmake file around for the same reason. This is annoying, for sure, but it seem to me that it is a common issue. So for now just a few comments and clarifying questions from me.įorcing them to maintain a FindProj.cmake in their source tree. I am not the best to deal with this issue so I'm hoping to get input from and as well. (Maybe less in the PROJ case, but definitely in the general case.) reimplementing CMake config file generation in autotools is going to be a fruitless, volatile maintenance burden.I don't dispute that autotools works great for Debian packaging. autotools should eventually be dropped.the CMake build shall be adjusted to support Debian's multiarch builds of PROJ.the CMake build needs to create the missing pkgconfig files.It is kept for Debian stable, Ubuntu 18.04 and alikes, with PROJ version down to 4.9 where there are no CMake options. The CMake find module is not "maintained" for Debian testing / PROJ 8.0. #QMAPSHACK BUILD FINDPROJ4.CMAKE INSTALL#The developers of QMapShack and OpenOrienteering Mapper have complained that the Debian package does not install the CMake files forcing them to maintain a FindProj.cmake in their source tree. This header file was removed in PROJ 8.0.0, uncovering the unbalanced feature set of the PROJ build systems. ![]() This makes our package fall back to a legacy FindPROJ4.cmake which looks for proj_api.h. With the Debian PROJ package being build with autotools, it doesn't provide the CMake config files. Now we are using CMake, and we have been adopting modern PROJ and CMake early. #QMAPSHACK BUILD FINDPROJ4.CMAKE SOFTWARE#For more context, as the developer of OpenOrienteering Mapper:ĭebian claims that our software fails to build from source with PROJ 8.0.0, due to usage of proj_api.h. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |