Hello,
I have posted my question here because I forgot I was on this mailing list:
http://stackoverflow.com/questions/28773650/cmake-for-windows-dll-with-opencv-project
there you can find my Cmakelists.txt and some code snippets. This is my
first time trying to build a DLL for windows with CMAKE
Thanks for the help!
It still runs Release mode:
Here's my project:
https://github.com/acgetchell/CDT-plusplus
┌─[*adam*][Hapkido][*±*][master *✗*][~/CDT-plusplus]
└─▪ tree
.
|.git
| |config
| |description
| |HEAD
| |hooks
| | |applypatch-msg.sample
| | |com
That’s what I have been doing... :(
-Original Message-
From: John Drescher [mailto:dresche...@gmail.com]
Sent: Friday, February 27, 2015 8:33 AM
To: Scott Aron Bloom; CMake ML
Subject: Re: [CMake] Multi-platform visual studio projects
> I have been successful with
>
> Src\build.32 and s
> I have been successful with
>
> Src\build.32 and src\build.64 so that on svn update effects both.
>
> The problem, for my automated build flow, I was hoping to make a mix, 32/64
> installer.. it’s a lot harder to do with two completely separate build trees
> :(
For this I just make separate in
Thanks!
-Original Message-
From: John Drescher [mailto:dresche...@gmail.com]
Sent: Friday, February 27, 2015 8:26 AM
To: Scott Aron Bloom
Cc: cmake@cmake.org
Subject: Re: [CMake] Multi-platform visual studio projects
> However, once the solution is created, does the "path" of the shell
> However, once the solution is created, does the "path" of the shell matter
> at all?
No.
John
--
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 community. For mo
Thanks..
I have been successful with
Src\build.32 and src\build.64 so that on svn update effects both.
The problem, for my automated build flow, I was hoping to make a mix, 32/64
installer.. it’s a lot harder to do with two completely separate build trees :(
As to my second question, and this
On Fri, Feb 27, 2015 at 10:44 AM, Scott Aron Bloom
wrote:
> Is it possible with cmake, to build a VS 2013, win32 and win64 vsproj
> solution file set?
>
> If not, I understand, then I have a follow on question..
>
No create 2 independent trees. I keep the source in a separate tree
also. For examp
Is it possible with cmake, to build a VS 2013, win32 and win64 vsproj solution
file set?
If not, I understand, then I have a follow on question..
Once the two solutions have been built, does it matter how you bring up VS
2013? Or does it only matter for the initial running of cmake ?
Scott
--
On Friday February 27 2015 10:44:11 Omar Valerio wrote:
Hello Omar,
>Well yes I suggest you to use a FIND_LIBRARY directive inside your
>CMakeList.txt project file and HINT the compiler which location to prefer
>for the library to get linked. (
>http://www.cmake.org/cmake/help/v3.0/command/find_l
Hello,
I'm trying to build a project that uses FindPythonInterp.cmake to locate the
python executable. Thing is that the system I'm working on has "python"
pointing to a 2.7 install, while the project requires Python 3.x. Is there a
way to influence the search from the command line? I tried
-D
On Wed, Feb 25, 2015 at 10:45 PM, Stephen Kelly wrote:
> Kim Rydhof Thor Hansen wrote:
>
>> http://www.cmake.org/cmake/help/v3.0/prop_tgt/AUTOGEN_TARGET_DEPENDS.html
>>
>> I have a similar problem because automoc doesn't pick up that my
>> metadata.json file is a dependency to the generated moc_pl
12 matches
Mail list logo