[CMake] -DCMAKE_BUILD_TYPE=Release breaks build process

Hi all, I'm relatively new to cmake and tried to use it for one of my projects. Meanwhile I've got a working version, but when I try to build with -DCMAKE_BUILD_TYPE=Release the linker complains about missing functions. I guess, that this happens, because all the files are compiled separately

Re: [CMake] -DCMAKE_BUILD_TYPE=Release breaks build process

Hi Berni, > On 2 Mar 2017, at 10:12, Bernhard Seckinger wrote: ... > but when I try to build with > -DCMAKE_BUILD_TYPE=Release the linker complains about missing functions. ... > Maybe you can give me some ideas on how to proceed? ... just a general idea as how to

Re: [CMake] -DCMAKE_BUILD_TYPE=Release breaks build process

02.03.2017, 13:58, " Jan Hegewald" : > Hi Berni, > >>  On 2 Mar 2017, at 10:12, Bernhard Seckinger >> wrote: > > ... >>  but when I try to build with >>  -DCMAKE_BUILD_TYPE=Release the linker complains about missing functions. > > ... >>  Maybe

[CMake] libsndfile in winodws

Hi all , I was trying to build my .cpp file in windows in Windows platform (windows 10) using cmake . My .cpp file makes use of two external libraries 1)armadillo 2)libsnd file. I have written a corresponding cmakelist.txt to compile and obtain the binary . I was successful in doing so in Linux ,

Re: [CMake] libsndfile in winodws

On 2 March 2017 at 12:07, aishwarya selvaraj wrote: > Hi all , > I was trying to build my .cpp file in windows in Windows platform (windows > 10) using cmake . > My .cpp file makes use of two external libraries 1)armadillo 2)libsnd file. > I have written a

Re: [CMake] libsndfile in winodws

On Thu, Mar 2, 2017 at 9:14 AM, Dave Flogeras wrote: > > Just my 0.02, but if I recall Eric doesn't (or didn't) support building > directly on Windows. > > Pardon me, that should be Erik -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ

Re: [CMake] libsndfile in winodws

On Thu, Mar 2, 2017 at 8:47 AM, aishwarya selvaraj < aishwaryaselvaraj1...@gmail.com> wrote: > @Dan Liew > Thanks for your feedback. > Yes I was trying to proceed in that direction . > Did you find any links which could be useful ? > could you kindly share them ? > Thanks > > Running a

Re: [CMake] -DCMAKE_BUILD_TYPE=Release breaks build process

Hi Jan, > just a general idea as how to approach this: > - make a clean cmake directory and try again, or at least remove the > CMakeCache.txt I'm allready doing this all the time... :-) > - if you use the make generator, add -DCMAKE_VERBOSE_MAKEFILE=ON when > calling cmake to know what exactly

Re: [CMake] libsndfile in winodws

@Dan Liew Thanks for your feedback. Yes I was trying to proceed in that direction . Did you find any links which could be useful ? could you kindly share them ? Thanks On Thu, Mar 2, 2017 at 5:08 PM, Dan Liew wrote: > On 2 March 2017 at 12:07, aishwarya selvaraj >

Re: [CMake] -DCMAKE_BUILD_TYPE=Release breaks build process

On 2017-03-02 13:01+0100 Bernhard Seckinger wrote: Basically it's (works) /usr/bin/gdc -I.. -fversion=slang -oCMakeFiles/starbattle.dir/__/puzzle -c /home/berni/Croco/Entwicklung/Croco/types/puzzle.d [...] /usr/bin/gdc CMakeFiles/starbattle.dir/starbattle

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc1-720-gdcb743e

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via dcb743e3f68638141d4c81f653a82b9082135f3f (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc1-718-g25dc8c0

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via 25dc8c09860498aaba135aed5a05fa3b55b304d0 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc1-722-g2d59003

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via 2d590038de63afa16ebb9197ca070aba1130c39e (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc1-726-g16114ac

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via 16114ac346e661d7b3bb50dfd09a1a8f361751a4 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc1-366-g2187818

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 2187818706241201b067605138bbcaea420411b5 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc1-393-gc1fb721

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via c1fb7213edaf512774eb74adb0a89b4984f88904 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc1-376-g6d9ab1e

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 6d9ab1eff7bd8a1374429c61627157dda4bb127b (commit) via

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc1-380-g5d81817

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 5d81817b7168d16190848807d2cfb73ed14b8ee7 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc1-382-g6c332bd

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 6c332bd84ce320e4163130a052af7b9950b38318 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc1-743-gb1b6156

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via b1b6156cca4068dee0cfd0ec9c1fd6f2e7513db5 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc1-736-ga27f743

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via a27f7433686292d5c54d42c394bd620da3b3c2d6 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc1-745-g3bf5d33

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via 3bf5d33ba90dc3478a928f47507e004d905b7d87 (commit) via

[cmake-developers] [ANNOUNCE] CMake merge process transition

Hi Folks, We're moving CMake's process for merging changes to new infrastructure that is managed directly within merge requests on gitlab.kitware.com. Summary --- The new process for reviewing changes, staging them for nightly testing, and eventually merging to `master` is documented in a

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc1-750-gb1cf272

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via b1cf272646abab16e53bc3e7083629ee23ec089d (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc1-747-g8324210

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via 83242107ad6514dff6a8b6946467838f4d4104be (commit) via

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc1-395-g06ef23c

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 06ef23c3e0abf79f451cf69fbd3ac646b7e17c27 (commit) via