; On Fri, Sep 18, 2015 at 5:42 PM, Joe wrote:
> > Hi. I was hoping to get some guidance on if this is bad practice. I am
> > simply trying to find a way to manage internal dependencies of my project
> > but with a file structure that is distributed. It looks like this:
> &g
Hi. I was hoping to get some guidance on if this is bad practice. I am
simply trying to find a way to manage internal dependencies of my project
but with a file structure that is distributed. It looks like this:
/path/to/A
/path/to/B
B depends on A. I cannot change this directory structure.
wrote:
> On 11/17/2014 1:44 PM, Joe wrote:
>
>>
>> 1) How can the same ARGV to the same function give different ARGN's? My
>> feeling is that the answer is "never, it's something in how the MESSAGE
>> command displays lists."
>> 2
Hey all,
I know that ARGV is all arguments, and ARGN is all arguments past the last
expected argument. I find myself in a weird situation with these, where
identical ARGV's in the same function lead to different ARGN's. The
relevant code in the CMake script is below
FUNCTION(MY_FUNC_NAME EXE_NAME
> CPACK_RPM_DEBUGINFO which would trigger the feature.
>
> Is the debuginfo generation distribution-specific or is it the same
> for Fedora, Mandriva, OpenSuSE or any other RPM-based distro?
I verified that the RPM macros exist on CentOS, Fedora, Ubuntu (with
RPM tools), and Mandriva.
J
lays nice with CPack? Or is there an
alternate way to generate debuginfo packages for RPM platforms within the
confines of CMake/CPack?
joe
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic
ture, I'll probably need to build the program separately in 10.7 in
order to run it in 10.7.
And thanks David, your posts have been very helpful.
Best,
Joe
On Tue, May 22, 2012 at 12:06 PM, Michael Jackson
wrote:
> It seems that this library is ONLY installed with Xcode which leads me
well. The solution I see so far is to copy the
.dylib into Lion.
-Joe
On Tue, May 22, 2012 at 11:35 AM, Michael Jackson
wrote:
> You have a bad install of Lion (OS X 10.7.x). I just checked 3 different Lion
> machines and ALL have OpenCL.framework installed. So I would suspect your
> Lion
ly copy the framework into the bundle
> rather than selectively copying just the framework library and its
> "Resources" folder.
>
> I am very hesitant to recommend copying a "/System" framework into a bundle
> without knowing more details about where that framework c
o "other". Just add another chunk inside your override function that
> looks like this:
>
> if(resolved_file MATCHES
> "^/System/Library/Frameworks/OpenCL.framework")
> message("resolving ${resolved_file} as other")
> set(${type_
GetPrerequisites.cmake but didn't get any
clue how to do that.
Thanks,
Joe
On Mon, May 14, 2012 at 8:47 PM, David Cole wrote:
> Rather than just doing a "fixup_bundle" as an INSTALL(CODE snippet, put it
> in a separate CMake script, and use install(SCRIPT to execute it. You can
> c
Thanks, this is exactly what I need.
Just one question. Why the function gp_resolved_file_type_override()
cannot be seen if it is implemented in my project's CMakeLists.txt? I
have to add it in GetPrerequisite.cmake module, but that's not good.
Thanks,
Joe
On Mon, May 7, 2012 a
xup_bundle() to fix dependencies for
architecture ppc7400, but the error remains.
Any idea how to get around this?
Thanks,
Joe
--
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 check t
list.
On Fri, Nov 18, 2011 at 8:16 AM, Michael Hertling wrote:
> On 11/17/2011 05:53 PM, Joe Brandt wrote:
> > I totally agree with your #2. I was thinking that it would be easier to
> > try and update the existing ones, rather than create new ones, at least
> > from the p
at 6:27 AM, Michael Hertling wrote:
> On 11/17/2011 12:28 AM, Joe Brandt wrote:
> > I have a couple issues, that I'd like to help fix, with the current
> > FindTCL.cmake, FindTclsh.cmake, FindWish.cmake, and FindTclStub.cmake
> that
> > make them unusable for me. Th
r, can
get incorporated back upstream.
Joe
--
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 check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubsc
Hi,
I've got a seemingly simple question. However, I failed to find an answer up to
now.
In my FindXXX module, I search a library with help of the find_library command
on a 64-bit Linux. Now, I want to check, if the library is 32-bit (built with
-m32) or 64-bit.
How can I check this?
Thanks
Hi all!
I have a project, which pulls in a bunch of sub-projects, using
add_subdirectory.
The problem is that these projects all create a custom target called
uninstall. Obviously, when these projects are pulled together, the uninstall
targets clash.
An ideal solution would be to ignore the unins
lps.
"
After doing this I thought to set cmake as 'run as admin', and that seemed to
get everything to generate as it should.
Thanks,
Joe
From: Bill Hoffman
To: David Cole
Cc: cmake@cmake.org
Sent: Tue, January 5, 2010 3:01:47 PM
Subject: Re: [CMa
I deleted the whole build directory before running the build. There isn't any
modifying of the CMakeCache.txt as far as i know.
Joe
From: Smith Jack (Ext. - UGIS - UniCredit Group)
To: "cmake@cmake.org"
Sent: Tue, January 5, 2010 8:24:51
or:
CMake Error: Could not COPY_FILE.
OutputFile: ''
copyFile:
'C:/Users/joe/devel/RUGUD-devel/com.ara.engen.plugins.cpp/build/windows.AMD64.vc.8.release/CMakeFiles/CMakeDetermineCompilerABI_C.bin'
Unable to find executable for try_compile: tried
"C:/Users/joe/dev
Hi,
I am currently writing a FindXXX.cmake file which uses find_path to find
an include path. Unfortunately it turns out that there might be several
versions of the file in the PATHs/HINTS (e.g. several revisions of the
package). (I handle this with test using the try_compile command).
My ques
Hi,
we have started to migrate the build system of our
software to cmake. After a great success in starting
the new build system some questions arise, when
thinking about mid and long term maintainability.
When writing own FindXXX.cmake modules, it seems to be
of advantage to follow the same conve
23 matches
Mail list logo