be able to do
common tasks using INSTALL(SOMETHING) to e.g. run fixup for you
without having to use another script or INSTALL(CODE).
--
Mike McQuaid
http://mikemcquaid.com
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://w
rs to pick apart.
I would agree with this. There's probably a fair amount of wiki
organisation that could be done (which I guess I could help with too)
and some of it could be rolled into the main CMake documentation
perhaps (such as variable descriptions).
I too would love more development/
iling list. Write some tested, documented code and
> contribute it.
Great, I think I understand how to do that a bit better now. It would
be great if the contents of your email above was included here:
http://www.cmake.org/cmake/project/getinvolved.html and also possibly
on
less code writing.
> Again, let me stress, no offense taken. There is no way you can offend me,
> unless you start calling me names for no reason. Reasonable discussion
> always welcome.
So can I call you names as long as I have a good reason? ;)
--
Mike McQuaid
http://mikemcquaid.com
I don't cause any offense here either. I'm passionate about
CMake because I like the tool and want to make it better.
--
Mike McQuaid
http://mikemcquaid.com
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://w
o).
I agree. I think the install-time/CPack/dependency stuff needs some work.
--
Mike McQuaid
http://mikemcquaid.com
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please k
is stuff but I create
bugs and they are ignored and then post on the mailing list and no-one
from Kitware comments. I really appreciate that everyone is very busy
but it feels like the CPack developers think it's good enough as-is
and aren't particularly interested in attracted new
ds like a perfect
argument for this module existing in some form.
This is definitely something non-intuitive about using CMake with
Visual Studio. It would be good if these sort of rough edges could be
sorted out with modules.
--
Mike McQuaid
http://mikemcquaid.com
_
ugins
"belong" to what modules.
--
Mike McQuaid
http://mikemcquaid.com
___
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
rly) intelligently loops through and
adds variables for every single plugin. Would love to get it merged.
--
Mike McQuaid
http://mikemcquaid.com
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/open
eport about this:
http://public.kitware.com/Bug/view.php?id=11141
--
Mike McQuaid
http://mikemcquaid.com
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messag
either the documentation or
the code fixed to use the documented variable.
I've filed a bug report about this:
http://public.kitware.com/Bug/view.php?id=11127
I'm happy to work on a patch if we can agree on a best approach.
--
Mike McQuaid
ht
ional, let me know and I'll create a patch.
I also filed a bug about this:
http://public.kitware.com/Bug/view.php?id=11143
--
Mike McQuaid
http://mikemcquaid.com
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http
sites cannot help with this.
I've created an initial patch here:
http://public.kitware.com/Bug/view.php?id=11145
I think this is another thing that will help in the deployment of Qt
applications using CPack.
--
Mike McQuaid
http://mikemcquaid.com
_
;m trying to use it for some open-source projects
and producing decent Mac KDE binary packages.
This is a problem that I keep running into again and again and
currently there isn't a nice solution. When I show people
INSTALL(CODE) blocks or external scripts required for the above, they
go "
my experience, literally every time I've used
CPack for a project or recommended it to others they've required this
functionality. That's not to say that it is used in every single
project using CPack out there but it seems to be necessary to a lot of
users.
--
Mike McQuaid
http://mikem
On 20 December 2010 12:34, David Cole wrote:
> On Sun, Dec 19, 2010 at 3:50 PM, Mike McQuaid wrote:
> When you find yourself in the "must escape too much" situation in an
> INSTALL(CODE scenario you should switch to writing out a script that you
> then include with an
t; )
However, you then need to put all your CMake logic in INSTALL(CODE
...) logic. Either later tonight or tomorrow I'll post my suggestions
to this list for possible patches I will try and get included to
improve this situation as INSTALL(CODE ...) escaping isn't trivial.
--
Mike Mc
to run CMake ONCE (as you said developers rarely ever touch
CMake files).
If you want to use Makefiles, fine, but without benchmarks your argument is
pretty meaningless FUD against CMake and other makefile generators.
--
Cheers,
Mike McQuaid
http://mikemcquaid.com
_
ve worked on don't keep any generated files in version control,
be it from the makefile generator, code generator or binary files.
--
Cheers,
Mike McQuaid
http://mikemcquaid.com
___
Powered by www.kitware.com
Visit other Kitware open-source pro
efiles.
Basically, your options are using the version of mingw provided with cygwin or
using the CMake Windows version and remembering to specify mingw-make as the
generator from the GUI.
--
Cheers,
Mike McQuaid
http://mikemcquaid.com
___
Powered by
ant to
> have to use it), but when I run cmake is still picks up /usr/bin/c++.exe at
> the default and tries to compile using /home for all the paths.
To do this you need to use a version of CMake compiled in Cygwin. I'm pretty
sure a binary package is available in the package manag
/else statements depending on your
platform and just use a different build directory for each platform,
then each will have a different build folder but also a different
CMake cache so the variables will be parsed differently.
--
Cheers,
Mike McQuaid
http://mikemcquaid.com/
___
; what it is, and if other unix users have issues, we can fix the cmake
> file then. The typical sloppiness of someone not dealing with their
> native platform, I guess :)
>
> There are other problems with converting this file, but I want to
> start w
install target, then
> run the regular one, having put the install location of the libraries into
> your RUNTIME_LIBRARY_DIRS)
Another alternative would be to use InstallRequiredSystemLibraries,
BundleUtilities and/or GetPrerequisites.
--
Cheers
creates a binary package for distribution. In this case,
they will have the various libraries already on their system but the end-user
of the package won't. As a result, they will want to ensure that these are all
distributed.
In short, the difference between 2) and 3) only really ma
velop these features, if they'd be accepted. It was
suggested that both would require Kitware buy-in before I should start working
on them.
Thanks!
--
Cheers,
Mike McQuaid
http://mikemcquaid.com
___
Powered by www.kitware.com
Visit other Kit
27 matches
Mail list logo
