Thank you Brad !
Apologies for the delay in response, but these two weeks I fished and not
programmed .
As I said, I'm new to developing CMake. Thank you for making the patch , but I
do not know what to do with it .
Your comments are very valuable for me. I will try to use them in the future
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=14935
==
Reported By:th.thielemann
Assigned To:
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=14936
==
Reported By:neologius
Assigned To:
Hi everybody there,
Subject says it all. See the attached patch please.
(Didn't care enough to leave hg for git to generate the patch. Sorry.)
# HG changeset patch
# User Ebrahim Mohammadi mebra...@gmail.com
# Date 1401098735 -16200
# Mon May 26 14:35:35 2014 +0430
# Node ID
Hi everybody there,
Subject says it all. See the attached patch please.
(Didn't care enough to leave hg for git to generate the patch. Sorry.)
FILE_PATH is likely to contain C: or some other drive letter on
Windows. It is therefore unsuitable for using to construct a sub-path
underneath
${FILE_PATH} is PATH part of ${FIL} and ${FIL} is path of each of .proto
files relative to CMakeLists.txt as the user has entered in CMakeLists.txt.
So ${FIL} and consequently ${FILE_PATH} cannot contain drive letters in a
genuine usage scenario. Or I'm missing something.
On Mon, May 26, 2014 at
Maybe I'm missing something. Is it guaranteed that all callers of
PROTOBUF_GENERATE_CPP will pass non-full-path names for the .proto
source files?
If so, then I retract my statement. But I don't think you can guarantee
that.
David C.
--
Powered by www.kitware.com
Please keep messages
I think the user is supposed not to pass full paths to
PROTOBUF_GENERATE_CPP. Because if user does so, there is a more severe bug
right now in the code: if user provides both /some/path/A.proto and
/another/path/A.proto to PROTOBUF_GENERATE_CPP, C++ file of both A.proto
files will be generated in
... Long story short I think it is safe to assume ...
It is never safe to assume anything. I don't have personal experience
with protobuf
But in general, inputs to CMake are allowed to be full path or not, and
when not, they're usually treated relative to CMAKE_CURRENT_SOURCE_DIR.
Hi!
i had a problem between depencendies of static libraris. Due to the used tools
(qt, moc, uic) a library depends on another library, especially on header files
generated by uic.
This is a litte bit a broken design, but cannot fix it currently.
On massive parallel builds ( 8 cores on ssd )
Jörg Kreuzberger wrote:
Hi!
i had a problem between depencendies of static libraris. Due to the
used tools (qt, moc, uic) a library depends on another library,
especially on header files generated by uic.
This is a litte bit a broken design, but cannot fix it currently.
On massive parallel
My way of dealing with this problem is similar to other people here:
1. I have a separate Python post-build script designed to be driven
through command line.
This script read somewhere the list of direct binary dependencies of
the target[1] and copy them in the
output directory. The
On Mon, May 26, 2014 at 8:04 AM, Klaim - Joël Lamotte mjkl...@gmail.com wrote:
- Why can't I use the install command from CMake? My understanding is that
it's used to install the application in the system
Not really. It's to massage the installed files into their final form --
but not
Hi
How to force CMAKE to search for executables in /usr/local/bin first, not
in /bin?
I have:
FIND_PROGRAM(FLEX_EXECUTABLE flex PATH /usr/local/bin DOC path to the flex
executable NO_DEFAULT_PATH)
But this is not proper way to.
Regards
niespodd
--
Powered by www.kitware.com
Please keep
On Mon, May 26, 2014 at 5:08 PM, Dan Kegel d...@kegel.com wrote:
On Mon, May 26, 2014 at 8:04 AM, Klaim - Joël Lamotte mjkl...@gmail.com
wrote:
- Why can't I use the install command from CMake? My understanding is
that
it's used to install the application in the system
Not really. It's
o/
Just for the record, I solved the issue: if there are empty *.ts files
lupdate will fail to populate them.
Regards
On Fri, May 23, 2014 at 2:25 PM, Sergio Vera sergio.v...@alma3d.com wrote:
Hello fellow CMakers
I'm following the CMake guide to Qt based internationalization of my app:
On Mon, May 26, 2014 at 8:04 AM, Klaim - Joël Lamotte mjkl...@gmail.comwrote:
My way of dealing with this problem is similar to other people here:
1. I have a separate Python post-build script designed to be driven
through command line.
This script read somewhere the list of direct
So... no alternatives to location in this instance?
On Sat, May 24, 2014 at 7:28 PM, J Decker d3c...@gmail.com wrote:
CMake Warning (dev) at
C:/general/build/android/karaway/debug_out/core/DefaultInstall.cmake:203
(get_property):
Policy CMP0026 is not set: Disallow use of the LOCATION
Maybe you can explain _why_ you need to do it this way? Can it be solved more
inline with the better cross-compile support in cmake-3.0?
On 26. Mai 2014 19:29:20 MESZ, J Decker d3c...@gmail.com wrote:
So... no alternatives to location in this instance?
On Sat, May 24, 2014 at 7:28 PM, J Decker
if it exists as a target; I need to know the path to the built library for
subsequent projects to link against. I have to manually add the option
-Lpath to build library) -lbaselibname to avoid having the full path
linked into the resulting .so.
if I just use 'add_link_library' then the
20140526)
+set(CMake_VERSION_PATCH 20140527)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
21 matches
Mail list logo