On Fri, Apr 12, 2013 at 11:58 AM, Rolf Eike Beer wrote:
> Lloyd wrote:
> > Hi,
> >
> > I am new to Cmake and at present exploring its features for migrating our
> > projects build system to use it.
> >
> > I have main source folder inside that another folder contains the source
> > for our custom
Lloyd wrote:
> Hi,
>
> I am new to Cmake and at present exploring its features for migrating our
> projects build system to use it.
>
> I have main source folder inside that another folder contains the source
> for our custom library.
>
> I understand that the problem is with my cmake file. Thro
Hi,
I am new to Cmake and at present exploring its features for migrating our
projects build system to use it.
I have main source folder inside that another folder contains the source
for our custom library.
I understand that the problem is with my cmake file. Through that the
generated project
Thu, Apr 11, 2013 at 4:01 PM, Clinton Stimpson wrote:
> Why do you have this CPack generator creating the .app instead of letting
> the
> CMake build step create the .app from the add_executable( ...
> MACOSX_BUNDLE ..
> )?
>
Because I was so happy to have it working I forgot to refactor the cod
On Thursday, April 11, 2013 03:30:39 PM Brian Milco wrote:
> Hi,
>
> I've added a CPack package generator for the Mac App Store for your
> consideration. You can find it on github:
> https://github.com/iPenguin/cmake/tree/cpack-mac-app-store-generator
>
> This is a first draft, but it should work
Hi,
I've added a CPack package generator for the Mac App Store for your
consideration. You can find it on github:
https://github.com/iPenguin/cmake/tree/cpack-mac-app-store-generator
This is a first draft, but it should work to get a basic application
uploaded via Apple's "Application Loader". I
On 11. april 2013 21:31, Matthew Woehlke wrote:
>> Where do I submit the merge request? Open a bug report?
>
> I would recommend following the 'share a topic' instructions at
> http://www.cmake.org/Wiki/CMake/Git/Develop.
Thanks for the link, but I feel this is more for module keepers, and
this i
Matthew
On 2013-04-11 14:58, Yngve Inntjore Levinsen wrote:
I have now finished a patch which I am quite sure does not break old
logic, while fixing this problem. It should be said that I know little
about code conventions and it is perhaps not as pretty as it could be,
so please feel free to c
On 21. mars 2013 18:30, Rolf Eike Beer wrote:
> Yngve Inntjore Levinsen wrote:
>> > On 21. mars 2013 12:00, Rolf Eike Beer wrote:
>>> > > Am 21.03.2013 11:03, schrieb Yngve Inntjore Levinsen:
> >> Hi,
> >>
> >> I have a suggestion for the PythonInterp. On a system I am compiling
>>
On Apr 11, 2013, at 11:27 AM, Braden McDaniel wrote:
> On Apr 1, 2013, at 3:10 PM, Micha Hergarden wrote:
>
>> On 01-04-13 20:02, Braden McDaniel wrote:
>>> When mixing a CMake Visual Studio build that has ExternalProjects (that is,
>>> via ExternalProject_Add) that use non-CMake makefile buil
> Did you try protecting the $ that needs to be with \$
> Or
> set(PDOLLAR "$") and use ${PDOLLAR}
This is a pretty ugly hack, but also the one suggestion that actually
worked. Thanks!
--Nico
On Wed, Apr 10, 2013 at 8:49 PM, Eric Noulard wrote:
>
>
>
> 2013/4/10 Nico Schlömer
>>
>> Hi all,
On Apr 1, 2013, at 3:10 PM, Micha Hergarden wrote:
> On 01-04-13 20:02, Braden McDaniel wrote:
>> When mixing a CMake Visual Studio build that has ExternalProjects (that is,
>> via ExternalProject_Add) that use non-CMake makefile builds, how does one
>> resolve the mismatch between the *_ varia
Thanks that was it!
On Thu, Apr 11, 2013 at 9:02 AM, David Cole wrote:
> Try:
>
> cmake -D "DOXYGEN_TAGFILES:STRING=C:/bar/somevalue=C:/foo/another" -P
> configure_file.cmake
>
> Because of the “:TYPE” parsing, “:” after the = sign can sometimes be
> misinterpreted by the regex code used to p
Try:
cmake -D "DOXYGEN_TAGFILES:STRING=C:/bar/somevalue=C:/foo/another" -P
configure_file.cmake
Because of the “:TYPE” parsing, “:” after the = sign can sometimes be
misinterpreted by the regex code used to parse these out...
HTH,
David
From: Robert Dailey
Sent: Thursday, April
Actually I did a bit more testing on this:
C:\Work\rdailey-hp\dpd-cmake\cmake\scripts\cmake>cmake -D
"DOXYGEN_TAGFILES=C:/bar/somevalue=C:/foo/another" -P configur
e_file.cmake
DOXYGEN_TAGFILES:
C:\Work\rdailey-hp\dpd-cmake\cmake\scripts\cmake>cmake -D
"DOXYGEN_TAGFILES=C/bar/somevalue=C:/foo/ano
I'm invoking cmake -P to execute a CMake script in a custom command,
and I also pass in variables via -D. Here is the command that gets
generated by CMake for the custom command:
"C:\Program Files (x86)\CMake 2.8\bin\cmake.exe" -D
IN_FILE=C:/Work/rdailey-hp/dpd-cmake/server/gmmserver/domino/server
16 matches
Mail list logo