On 22 March 2013 18:01, Sergei Nikulov wrote:
> 2013/3/22 Mateusz Loskot
>>
>> I'm trying to build software which uses libE57 library which has
>> Xerces as dependency.
>> I build Xerces too as part of my project and I deploy it in custom
>> locations
On 22 March 2013 21:25, Andreas Stahl wrote:
> Am 22.03.2013 um 16:59 schrieb Mateusz Loskot :
>>
>> I'm trying to build software which uses libE57 library which has
>> Xerces as dependency.
>> I build Xerces too as part of my project and I deploy it in custom loc
On 23 March 2013 14:29, Alexander Neundorf wrote:
> On Friday 22 March 2013, Mateusz Loskot wrote:
>> On 22 March 2013 18:01, Sergei Nikulov wrote:
>> > 2013/3/22 Mateusz Loskot
>> >
>> >> I'm trying to build software which uses libE57 library which h
f the issues of fragmentation
and distribution, and it's time to apply "Stop Rolling Your Own" [1]
approach, and perhaps stream all those precious efforts into one sink.
[1] http://ithaca.arpinum.org/2013/01/02/git-prompt.html
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
t; This is just my opinion, and I would love to hear what others think. But
> you'll be hard-pressed to convince me that a find module inside CMake itself
> is better than a config file installed with a project's install tree.
I prefer to adopt what CMake recommends myself.
Best reg
.
As user and contributor to GNU Autoconf Archive [1],
I believe it's best option. I submitted modules there and
since then I received lots of patches through that repo
http://savannah.gnu.org/projects/autoconf-archive/
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
--
Powered
an add yet
> another find module into CMake.
Great, I'm all for that, but let's set up "no new find modules added
to CMake repo"
once for all, and force this approach.
Otherwise, reality will continue to diverge from the plans.
Best regards,
--
Mateusz Loskot, http://mateusz.
On 29 March 2013 18:31, Bill Hoffman wrote:
> On 3/29/2013 11:27 AM, Mateusz Loskot wrote:
>>
>> Great, I'm all for that, but let's set up "no new find modules added
>> to CMake repo"
>> once for all, and force this approach.
>> Otherwise, re
On 29 March 2013 21:00, Bill Hoffman wrote:
> On 3/29/2013 3:53 PM, Mateusz Loskot wrote:
>>
>> What if there are multiple CMake modules for the same project, all
>> different
>> and none offering complete coverage of features?
>
> Then they don't sounds rea
On 4 April 2013 17:44, Alexander Neundorf wrote:
> On Thursday 28 March 2013, Mateusz Loskot wrote:
>>
>> To CMake maintainers,
>> what do you think about creating new repository at
>>
>> https://github.com/Kitware/CMakeModules
>>
>> as incubator for
On 4 April 2013 20:14, Alexander Neundorf wrote:
> On Thursday 04 April 2013, Mateusz Loskot wrote:
>> On 4 April 2013 17:44, Alexander Neundorf wrote:
>> > On Thursday 28 March 2013, Mateusz Loskot wrote:
>> >> To CMake maintainers,
>> >> what do
anything changed in recent CMake versoins,
so it is no longer necessary.
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
--
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 che
ttp://cmake.org/cmake/help/v2.8.11/cmake.html#command:if
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
"Participation in this whole process is a form of torture" ~~ Szalony
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake
he build
> without any need to know the list's name or ensure it's
> definition reaches the scope at the top of the call stack.
Robert,
Am I getting it right, that you are trying to set a custom
user-defined property with set_directory_properties (or set_property),
like here:
set_dire
[1], but COMPONENTS is dedicated
to request lookup for the Boost libraries which are built as binary components.
For the Spirit, you just need to check if you have Boost headers available:
find_package(Boost 1.49 REQUIRED)
[1] http://cmake.org/cmake/help/v2.8.11/cmake.html#module:FindBoost
Bes
fying
COMPONENTS spirit
leads to lookup for non-existent binary library.
Perhaps, all headers-only libraries could be handled by the FindBoost module
and then reported by CMake:
"Spirit is headers-only, shall not be specified with COMPONENTS"
Best regards,
--
Mateusz Loskot, http://mateusz.
Hi,
The latest version linked in the documentation [1] is 2.8.11.
Where can I find docs for the latest release?
[1] http://cmake.org/cmake/help/documentation.html
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
--
Powered by www.kitware.com
Please keep messages on-topic and
On 11 October 2013 15:23, Robert Maynard wrote:
> I am currently in the process of getting the 2.8.12 documentation
> generated and uploaded.
Sweet, thanks!
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
--
Powered by www.kitware.com
Please keep messages on-topic and che
dllexport and dllimport.
IMO, OP should split the threads for sake of the list usability.
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
--
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 vari
wed by the platform name to
create project files for a specific target platform. E.g. "Visual
Studio 10 Win64" will create project files for the x64 processor;
"Visual Studio 10 IA64" for Itanium.
"""
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
--
On 4 November 2013 15:16, dravion.sm...@gmx.net wrote:
> Am 04.11.2013 16:09, schrieb Mateusz Loskot:
>>
>> On 4 November 2013 14:45, dravion.sm...@gmx.net
>> wrote:
>>>
>>> Hi,
>>>
>>> Is there an Way to choose diffrent Windows Com
On 4 November 2013 15:38, Bill Hoffman wrote:
> On 11/4/2013 10:21 AM, Mateusz Loskot wrote:
>>
>> I don't care about MinGW/Cygwin myself, but AFAIR, there is no
>> detection mechanism
>> for those, only -m64 flag juggling.
>
> You could look at the com
dditionally this sets the variables _BINARY_DIR and
_SOURCE_DIR to the respective values.
"""
> And they are the same as CMAKE_BINARY_DIR , or CMAKE_SOURCE_DIR.
>
> So why one would use the ${PROJECT}_BINARY_DIR variables?
i.e. when writing general purpose macros/fun
1 and statically link programs to it as needed (i.e.,
> without installing library1's headers and binaries to the installation
> destination).
Jeet,
Have you managed to solve this task of combining use of git submodule
and exported targets without installation?
Anyone, is it even possible
Hi,
I've started adding the config mode support to my CMake-based
projects and with quite a success.
So far, I have basic understanding of what it takes in practice to enable
config mode and there is still more to learn for me.
TL;TR: How to make use of CMAKE_BUILD_TYPE in config mode?
Could any
On 17 December 2013 02:29, J Decker wrote:
> build with multiple passes... 1 time release, and 1 time debug. Don't
> think about building both at once
I'm more concerned about using both (linking against) at once,
FooBarUser built in Release links against FooBar build in Release mode...
AFA
On 17 December 2013 14:27, J Decker wrote:
> which is... build seperately into seperate directories even with makefile.
> [...]
Yes, and that is a good feature of CMake.
What is still unclear to me is how the package registry works in such case.
Here is the basic example to support my previous q
201 - 227 of 227 matches
Mail list logo
