Hi Namik,
> @Namik: Please do not put any system-specific paths like
> "C:/zlib/..." into the build files (both QMake and CMake). Use
> relative paths with respect to the source directory in order to
> support so-called out-of-source builds.
>
>
> Of course, I understand. The few absolute-path folder includes were the
> result of my frustrated attempts to make CMake properly include
> everything. As for the "C:/zlib" stuff, I really don't see any other way
> to use zlib at the moment... Until zlib is integrated into the CMake
> build, I have to provide libarchive with an absolute path to my local
> zlib installation.
Ok, I'll check this tonight on my Windows machine.
> This works fine and results in an executable popping up.
>
>
> Unfortunately, this is not true in my case. The build process behaves
> just like before. It compiles fine, and (apparently) even links against
> libarchive. However, attempting to start the program results in a crash.
> All I get is this: The program has unexpectedly finished.
Can you run this in a debugger in get more information on what and where
it crashed?
> There's got to be something wrong with the way libarchive is linked in
> CMake: target_link_libraries(ViennaCL_Benchmarkarchive)
> I tried archive before, as well as libarchive, ${libarchive},
> ${archive}, adding manual cxx flag -llibarchive, using a custom variable
> poiting to a local libarchive dll... nothing worked.
Ah, this still needs to be converted to a static link. Shouldn't be too
hard...
Best regards,
Karli
------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls.
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
_______________________________________________
ViennaCL-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/viennacl-devel