I'll use it in the future.
Best regards, cen
On 11/20/19 3:16 PM, Kyle Edwards wrote:
On Wed, 2019-11-20 at 00:54 +0100, cen wrote:
Hi
I have an existing c++ exe project which I want to test with gtest.
I
have not yet found an easy way to keep the project as is and test it
directly s
#x27;t used it yet, but I believe the target property
https://cmake.org/cmake/help/latest/prop_tgt/VS_DEBUGGER_ENVIRONMENT.html
might help you.
Petr
On Wed, 20 Nov 2019 at 01:02, cen <mailto:imba...@gmail.com>> wrote:
Hi
Perhaps not really a cmake problem but here we go. An e
lines? Ideally my goal is to just run cmake, open VS, build the
project and run, all automagical.
I would prefer to keep the dynamic linking.
Best regards, cen
--
Powered by kitware.com/cmake
Kitware offers various services to support the CMake community. For more
information on each o
re.
Best regards, cen
--
Powered by kitware.com/cmake
Kitware offers various services to support the CMake community. For more
information on each offering, please visit https://cmake.org/services
Visit other Kitware open-source projects at https://www.kitware.com/platforms
Follow th
to #4.. to
automatically build the tested project and link to it's object files in
gtest project.
This seems to me to be a really obvious case for testing so I am not
sure whether it really is that complicated or I am doing things wrong.
Bets regards, cen
--
Powered by www.kitware.com
Pleas
nclude(Effective.cmake) in your CMakeLists.txt to enable all
warnings. The effort here is to compile a list of existing bad practices
and wrap them (if such a thing is possible).
Does this approach seem reasonable? Is there an effort with similar
goals out in the wild which I should know about?
25 napisal:
You need to set these compiler flags BEFORE the project() call to let CMake
detect all stuff properly. There is a CMake variable telling you the size of a
void*.
Am 29. Oktober 2016 12:22:07 MESZ, schrieb cen :
Hi
Once I switch to 32bit builds, CMake fails to recognise that
glibc-
Hi
Once I switch to 32bit builds, CMake fails to recognise that
glibc-devel.i686 is not installed resulting in an error when running make.
In the same way, my own FindGMP fails to recognize that gmp-devel.i686
is not installed. I need CMake to fail if these things are missing.
At least for the
Sorry for wasting your time, it does work indeed. I forgot to pull the
correct version of CmakeLists.txt on my debian machine..
Thank you.
Domen Vrankar je 25. 10. 2016 ob 21:48 napisal:
2016-10-25 16:59 GMT+02:00 cen <mailto:imba...@gmail.com>>:
Why is patch level not baked
t links have the proper patch level version so I guess it is
ultimately ok but kinda annoying.
Best regards, cen
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake com
Exactly on point, thank you.
Domen Vrankar je 04. 07. 2016 ob 08:44 napisal:
Hi,
I have a very standard CPack configuration for deb package. I have two
questions:
1. I generate the deb with: cpack --config CPackConfig.cmake -G "DEB"
This is supposedly a binary package but when I install it o
Hi
I have a very standard CPack configuration for deb package. I have two
questions:
1. I generate the deb with: cpack --config CPackConfig.cmake -G "DEB"
This is supposedly a binary package but when I install it on the machine
I see header files being installed in /usr/include.
Is this no
Funny you say that, -H and -B options are the only ones I actually use
all the time. I never really understood why these are not documented or
part of the man page. Is there an official reasoning behind this?
On 3. 04. 2016 10:49, Craig Scott wrote:
> It would seem that the undocumented -H and -B
13 matches
Mail list logo
