Hi all,
I couldn't help myself from trying to make a more convenient build process
for zlib and libarchive.
I added a new CMakeLists.txt to the external folder. It's purpose is to
build both zlib and libarchive in one go. It seems to work alright on my
machine. One CMake configure and one mingw32-make command generates the
library files for both zlib and libarchive. I don't know how robust the
process is, but it would definitely be neat to make it work in this way.
One thing to note is that zconf.h kept on being renamed to zconf.h.in by
CMake, which prevented compiling zlib. I had to manually rename it back to
zconf.h after each CMake configuring.
And if we were to go back to submodules, we could build all the
dependencies with no more than 4 commands:
1. git submodule update ---init (both zlib and libarchive automatically
fetched by git)
2. configure external CMake build (properly prepare libarchive with zlib)
3. generate external CMake makefiles
4. build the libs (generate zlib, then libarchive libs with one make
command)
Would this be a good solution to simplify the build process? Is it feasible?
Regards, Namik
On Sat, Aug 2, 2014 at 11:40 PM, Namik Karovic <[email protected]>
wrote:
> A few comments on my CMake build attempt:
>
> While I was able to get the project up & running, the procedure is far
> from pretty. There were several issues along the way:
>
> -I fail to see the difference between previous submodules usage and the
> current setup... In the end both libarchive and zlib are placed in the
> external folder. The only difference is that now we have to do more git
> bash commands to get there. What am I missing?
>
> -zlib compiled fine
> -libarchive had some issues with this:
> https://gitorious.org/cmake/cmake/commit/8088332178a9fb082dd387beae9b1f262615a228
> I had to apply the fix manually, no idea why they haven't pushed it to
> their master.
> Since I didn't create a build folder in the project source folder, I had
> to provide my own path to ZLIB_INCLUDE_DIR and ZLIB_LIBRARY.
> It compiled fine after that.
> -then came Benchmark GUI. Again, since I was using a different build
> folder, I had to do some path setting for zlib and libarchive. It compiled
> fine, but failed to run since libarchive.dll wasn't placed in the same
> folder as the exe. When I placed it there manually, it worked.
>
> While I'm glad it works alright now, I must say it's way more difficult
> than I'd like it to be. Is it maybe possible to make a dedicated CMakeLists
> file just for zlib and libarchive? That would make things significantly
> easier.
>
> Regards, Namik
>
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
ViennaCL-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/viennacl-devel
