Not all GDAL drivers are already supported by Borsch ( ). Just rewrite make/automake files to CMake it seems to me no sense and will not provide new quality (maybe vice versa). You cannot integrate CMake into GDAL tree not solving this problems. #Qmapshack build findproj4.cmake driverI think your proposal is a step aside (back?) and more suitable for your needs (refactoring a complex driver (GML)) but it will be regression for tasks I noted.įirst of all need the answers for my questions about dependencies, build on different platforms, support different compiles, IDEs and you may come to some kind of Borsch. The noted Linux (Debian) OS - it builds too (there are targets to create deb and rpm) and exists ppa which shows Ubuntu builds too.Īll steps you described in your plan were already done and I think the Borsch is the next logical step. There is a solution for prebuild vendor libraries - see and .ĭo you tested your solution with another modern IDSs like Qt Creator, Android studio, Xcode? What about static builds for all platforms?Īs I noted, Borsch already works with this modern IDEs and on different operation systems. Everything is build with the one compiler. In Borsch dependency can be added with the single line of code in CMake file. How do you plan to get iconv, json-c, geos, proj4, expat and other libraries especially on MacOS, Android, iOS builds (Windows too for specific compiler - see discussion around )? The changes added to GDAL sources tree make it more suitable to CMake ideology, modern GDAL 2.x and it complex (raster/vector/network) drivers, dependencies needs and provide more flexible approach for configuring the build.Īlso I don't see how you plan solve dependencies problem, which already solved in Borsch. The Borsch is not the project about rearrange GDAL sources tree. Drop legacy build system when every core developers satisfy CMake/IDE experiences. #Qmapshack build findproj4.cmake updateStill team will release binaries building with legacy build system.Īt this time, all contributor should aware that he/she should update both cmake and legacy one. Now it is a state of a technical preview.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |