SALVADOR wolfieyo
http://www.narcononfreedomcenter.com/wp-admin/images/79m9o.php?pkmac765¢dha6
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and
Sorry if this is not the correct list to post questions. Please direct me
to the proper place if so.
I'm having trouble linking my OS X application to a specific framework using
CMake without explicitly setting linker flags (somewhat defeating the
purpose of using CMake for cross-platform buildin
On 10/21/2011 06:49 PM, pellegrini wrote:
> Hi all,
>
> after digging and googling some hours I did a first step in the right
> direction.
>
> I had to add the command:
>
> enable_language(rc)
> set(cmake_rc_compiler_arg1 -cif8)
>
> The resource compiler I (must) use is the one provided by win
Yes, me -> http://public.kitware.com/Bug/view.php?id=12532
Don't think as a reporter you can even edit your own bug entries after
committing them. Or I'm missing a button somewhere.
Op 21 okt. 2011 om 20:20 heeft David Cole het volgende
geschreven:
> As an esteemed colleague has pointed out,
I did some searching and on stackoverflow I found a post that had code in it
to provide precompiled header support:
http://stackoverflow.com/questions/148570/using-pre-compiled-headers-with-cmake
Below is the relevant macro I am using from that post. Unfortunately this
does not seem to work when g
I have a folder with a bunch of cmake modules in it that contain my custom
CMake code used across all projects.
I only generate for visual studio, so I was thinking it would be useful to
have a dummy project in my solution named "_cmake" that contains nothing but
my *.cmake files in it.
How would
As an esteemed colleague has pointed out, those with "reporter" level
account in Mantis may not edit bugs other than their own directly.
So. if you are in that boat, but would like to vote for a bug fix
to be considered for 2.8.7, please reply to this thread, and just list
the bug number, or a
On Friday 21 October 2011, Dan Kegel wrote:
> Where I work, a lot of people use Eclipse, a few people use Xcode,
> a few people use Visual Studio, and a few people use vi and the
> commandline. (I'm in the latter camp, and have only moderate familiarity
> with IDEs.) Each camp seems to have a diffe
Hi all,
after digging and googling some hours I did a first step in the right
direction.
I had to add the command:
enable_language(rc)
set(cmake_rc_compiler_arg1 -cif8)
The resource compiler I (must) use is the one provided by winteracter
Fortran library.
This led me to a serie of problem
Hi all,
*NO* replies requested. Different technique this time. Please edit the
bug tracker directly. (Unless you have problems with the bug tracker:
if so, please feel free to reply here with your suggestions.)
We are planning for CMake 2.8.7, aiming for a December release. We're
targeting Dec. 2
On 10/06/2011 10:29 AM, Michael Wild wrote:
> On 10/06/2011 08:14 AM, Michael Hertling wrote:
>> On 10/06/2011 07:04 AM, Michael Wild wrote:
>>> On Thu 06 Oct 2011 05:17:00 AM CEST, Michael Hertling wrote:
On 10/05/2011 10:47 PM, Robert Dailey wrote:
> In my particular CMake project, I hav
Hi all,
I use CMake 2.8.5 on Linux and Windows machine to build a Fortran project.
On Windows, no problem, the build and the resulting GUI are OK. On
Linux, the build seems to
be OK but the resulting GUI gives an empty screen. Discussing with
Michael a few days ago made
me think that it could
Hi all,
with cmake 2.8.6 all my problems are solved,
I'm can easily recreate/replicate custom_target.
Thanks a lot!
Best regards
Lukasz
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and
On 10/20/2011 6:56 PM, David Cole wrote:
It's not a Windows 8 thing at all... Same symptom occurs on Windows 7.
It's CMake generating this incorrectly:
# Visual Studio 2011
When it should be generating:
# Visual Studio 11
Since the comment there does not start with the expected string,
14 matches
Mail list logo