2012/1/9 Eric Noulard :
> 2012/1/9 Deborah Pickett :
Hi Deborah,
> So go ahead for the bug report "File listed twice"
Just seen that you have already filed the bug reports, thanks.
Putting their refs here for others:
http://www.cmake.org/Bug/view.php?id=12863
http://www.cmake.org/Bug/view.php?i
2012/1/9 Deborah Pickett :
> Hi Eric,
>
> On 06/01/2012, at 7:36 PM, Eric Noulard wrote:
>
>>> From a ton of googling, consensus seems to be that for directories that you
>>> "know" are on the target system, you don't have to list them in the %files
>>> list. I'm confident that /etc/init.d is in
When MSBuild.exe is used (typically by "cmake --build") for building a
VS2010 project generated by cmake, it correctly invokes cmake for
regenerating the project files if changes to the CMakeLists.txt files
are detected. However, the build does not restart nor abort, so MSBuild
continues using the
On Sun, Jan 8, 2012 at 7:29 AM, Renato Utsch wrote:
> Hello, I have been experimenting some issue with visual studio and
> couldn't fix them, even when searching in google for help :O
>
> So, I have 2 main issues:
>
> 1. When CMake creates the visual studio solution, it configures to the
> "Debug
Hi Eric,
On 06/01/2012, at 7:36 PM, Eric Noulard wrote:
>> From a ton of googling, consensus seems to be that for directories that you
>> "know" are on the target system, you don't have to list them in the %files
>> list. I'm confident that /etc/init.d is in this category.
>
> I think you are
On Sunday, January 8, 2012, Fraser Hutchison <
fraser.hutchi...@googlemail.com> wrote:
> On 07/01/2012 14:41, David Cole wrote:
>
> On Fri, Jan 6, 2012 at 6:47 PM, David Doria wrote:
>
> On Fri, Jan 6, 2012 at 5:54 PM, Jean-Christophe Fillion-Robin
> wrote:
>
> Hi David,
>
> Not too long ago I wa
Thanks guys, I discovered this experimentally myself.
-rhl
On Tue, Jan 3, 2012 at 1:29 PM, Eric Noulard wrote:
> 2012/1/3 Alexander Neundorf :
>>> you basically want:
>>> set(CMAKE_FIND_ROOT_PATH "/you/local/install/dir")
>>> before calling find_package(...)
>>
>> No, please don't.
>> CMAKE_FI
Don't know if you read all the emails, but I already found a solution
to the problem with all exe's with one output dir.
If you are right about the list of solution configs, so my search ends
here, but I alredy solved the real problem, so it's ok...
Renato
2012/1/8 Fraser Hutchison :
> Hi Renato
I'm still seeing the issue where the individual projects fail to load with
the error message "ALL_BUILD" is targeting ".NETFramework,Version=4.0" when
running the VS 2011 generator on windows 8 with visual studio 2011 express
developer preview.
What I find interesting is that I find absolutely no r
CLIFFORD MAN, IT WORKED!
This was everything I was looking for. Thanks:
# Configure the release changes (optimization)
set( CMAKE_RUNTIME_OUTPUT_DIRECTORY "${CMAKE_BINARY_DIR}" )
foreach( CONF_TYPE ${CMAKE_CONFIGURATION_TYPES} )
string( TOUPPER "${CON
Hmm - that looks interesting. I didn't know about
SUPPORTS_PARALLEL_BUILD_TYPE - I'll have to review my setup with that
in mind.
Thanks!
On Sun, Jan 8, 2012 at 4:52 PM, J Decker wrote:
> if( SUPPORTS_PARALLEL_BUILD_TYPE ) # will be set in visual
> studio type projects...
> INSTALL
On Sun, Jan 8, 2012 at 4:59 PM, Renato Utsch wrote:
> Clifford, can you explain more what you said, I didn't understand...
>
> You said that you change the output directories for all the active
> configurations to the same directory? Well, how do you do that (if it
> is what you said)? This is ex
>My current work-around is to peg all of the output directories for all
>the active configurations to the same directory - that negates much of
>the benefit of multiple-configuration IDE options, but does at least
>result in the expected run-from-build-directory behavior. (It works
>for MSVC - we
On Sun, Jan 8, 2012 at 1:49 PM, Clifford Yapp wrote:
> I can say that in my particular case, in order to be able to
> successfully run compiled binaries from the build directory it is
> necessary to have a broad variety of files in a sane position relative
> to the compiled binary. So far as I kn
On Sun, Jan 8, 2012 at 1:08 PM, Michael Jackson
wrote:
> This is going to sound either harsh or "flame bait" but is written in all
> seriousness and with a lot of practical experience.
>
> When coming from a "makefile" based system like Unix and going to Visual
> Studio there are a few things y
I can say that in my particular case, in order to be able to
successfully run compiled binaries from the build directory it is
necessary to have a broad variety of files in a sane position relative
to the compiled binary. So far as I know, the only way I can do this
in systems that like to have mu
No, it is perfectly valid and I understand you, but the problem is
that I'm rewriting a broken CMake script from the eAthena project (a
ragnarök online emulator), and it has a very old basis that would
cause a lot of trouble to change.
The executables _have_ to be on the ${CMAKE_SOURCE_DIR} when b
This is going to sound either harsh or "flame bait" but is written in all
seriousness and with a lot of practical experience.
When coming from a "makefile" based system like Unix and going to Visual
Studio there are a few things you need to "give up on" (In my opinion). Visual
Studio (And Xco
On Sun, Jan 8, 2012 at 10:28 AM, Renato Utsch wrote:
> Ok, I will look at that so.
>
> But and the second problem? How can I redirect from the debug/release
> folder to the / folder of the project?
>
Provide INSTALL rules in the CMAKE and then build the INSTALL target?
>
> Renato
>
> 2012/1/8 Ma
2012/1/8 Renato Utsch :
> Ok, I will look at that so.
>
> But and the second problem? How can I redirect from the debug/release
> folder to the / folder of the project?
I guess the same answer is valid.
How do you do that with Visual Studio alone?
Doesn't Visual Studio create the subfolder on his
Ok, I will look at that so.
But and the second problem? How can I redirect from the debug/release
folder to the / folder of the project?
Renato
2012/1/8 Mateusz Loskot :
> On 8 January 2012 16:04, Eric Noulard wrote:
>> 2012/1/8 Renato Utsch :
>>> So I can do this by adding a command line para
On 8 January 2012 16:04, Eric Noulard wrote:
> 2012/1/8 Renato Utsch :
>> So I can do this by adding a command line parameter to do that. But
>> can't I simply set an option that behaves exactly as --config Debug ?
>
> May be you could try to find out how Visual Studio
> is choosing the default bu
Perfect, what you suggested works like a charm. Within a small macro I
am now running this code
set(EXPORT_TARGET_LIST ${ARGV})
foreach(TARGET_UID ${ARGV})
get_target_property(IA ${TARGET_UID} "IMPORTED")
if(IA)
list(REMOVE_ITEM EXPORT_TARGET_LIST ${TARGET_UID})
endif()
endforeach()
bef
Hi Eric,
On Sun, Jan 8, 2012 at 5:20 PM, Eric Noulard wrote:
> I'm not sure how you compile your example.
> Should they be built in-source?
> Do you create out-of-source build tree for each A,B,SomeProject?
I usually build out-of-source. What is built out-of-source is up to
the user. Typically,
2012/1/8 Hauke Heibel :
> Hi again,
>
> I created a little example that shows the problem. It won't actually
> compile anything but it should help in understanding my problem.
I'm not sure how you compile your example.
Should they be built in-source?
Do you create out-of-source build tree for each
Good idea, I will try ^^
Renato
2012/1/8 Eric Noulard :
> 2012/1/8 Renato Utsch :
>> So I can do this by adding a command line parameter to do that. But
>> can't I simply set an option that behaves exactly as --config Debug ?
>>
>
> May be you could try to find out how Visual Studio
> is choosing
2012/1/8 Renato Utsch :
> So I can do this by adding a command line parameter to do that. But
> can't I simply set an option that behaves exactly as --config Debug ?
>
May be you could try to find out how Visual Studio
is choosing the default built type?
In particular does this correspond to some
So I can do this by adding a command line parameter to do that. But
can't I simply set an option that behaves exactly as --config Debug ?
Renato
2012/1/8 John Drescher :
> On Sun, Jan 8, 2012 at 10:30 AM, Mateusz Loskot wrote:
>> On 8 January 2012 15:21, Renato Utsch wrote:
>>> Yes, but I want
On Sun, Jan 8, 2012 at 10:30 AM, Mateusz Loskot wrote:
> On 8 January 2012 15:21, Renato Utsch wrote:
>> Yes, but I want to be able to change with CMake, but if I can't do
>> that, at least I want to be able to set the default to the Release
>> version :X
>
> You have to understand there is diffe
But why CMake generates the Debug mode thing first, not the Release? I
can only configure this with msbuild executable? Because I can't find
it :X
I only need to make the Release mode the standard one, there isn't a
way to do that changing a configuration with CMake?
Renato
2012/1/8 Mateusz Losk
On 8 January 2012 15:21, Renato Utsch wrote:
> Yes, but I want to be able to change with CMake, but if I can't do
> that, at least I want to be able to set the default to the Release
> version :X
You have to understand there is difference between generators like
makefiles and generators for proje
Hi,
I have the following problem and any help would be appreciated.
I have a shared library B which links to another shared library A
(with the new LINK_PRIVATE flag specified and the linking is carried
out against A's target). In B's CMake file, there is an export
statement for the shared librar
Yes, but I want to be able to change with CMake, but if I can't do
that, at least I want to be able to set the default to the Release
version :X
Renato
2012/1/8 Rolf Eike Beer :
> Am Sonntag, 8. Januar 2012, 12:29:47 schrieb Renato Utsch:
>> Hello, I have been experimenting some issue with visual
Am Sonntag, 8. Januar 2012, 12:29:47 schrieb Renato Utsch:
> Hello, I have been experimenting some issue with visual studio and
> couldn't fix them, even when searching in google for help :O
>
> So, I have 2 main issues:
>
> 1. When CMake creates the visual studio solution, it configures to the
>
Hello, I have been experimenting some issue with visual studio and
couldn't fix them, even when searching in google for help :O
So, I have 2 main issues:
1. When CMake creates the visual studio solution, it configures to the
"Debug win32" mode, but I wanted to be able to choose from "Release"
to
35 matches
Mail list logo
