Whatever happened to this?
On Mon, Feb 16, 2009 at 2:50 AM, Philip Lowman phi...@yhbt.com wrote:
Hi,
Luigi suggested a kind of CMake ports system in a recent thread here on the
CMake mailing list. This would presumably be a system whereby popular 3rd
party dependencies which have not yet
On Saturday 07 March 2009 11:08:43 Pau Garcia i Quiles wrote:
Whatever happened to this?
It's here:
http://code.google.com/p/cmakeports/
People are talking on the group list here and some stuff has been committed.
Unfortunately I personally have the feeling that it's starting as a bit
Hi all,
I have a build system with several subtargets residing in respective
subfolders. What is important - I'm using common binary directory for
all targets. The command I use is:
ADD_SUBDIRECTORY( nth_subfolder common_binary_dir )
The common binary folder was chosen to have all static
On Sat, Mar 7, 2009 at 6:42 AM, Peter Drahos drah...@gmail.com wrote:
Hi,
I'm one of the developers of LuaDist (Lua module distribution and build
system) that uses CMake for building. Its rather simple ports-like tool
that can install Lua modules and few libraries that we CM'd, including
On 6. Mar, 2009, at 16:44, Bill Hoffman wrote:
Marcel Loose wrote:
After further inspection, I think my observation holds true for all
Check*.cmake files in the Modules directory, not just the
CheckC(XX)SourceCompiles files.
It is a cache variable so that the test is not run over and over
some follow-up to my previous post:
I don't see an easy way to fix the presented problem within cmake
scripting mechanisms other than adding own script called at the setup
time for dependencies check and adding those dependencies to objects
using SET_PROPERTIES* directives.
However, as far as I
Wojciech Migda wrote:
Hi all,
I have a build system with several subtargets residing in respective
subfolders. What is important - I'm using common binary directory for
all targets. The command I use is:
ADD_SUBDIRECTORY( nth_subfolder common_binary_dir )
Each directory must be unique.
Hi again,
this workaround seems to do a trick:
in cmDependsC::WriteDependencies I've added a local variable to store
path to the source file being scanned for dependencies:
std::string root_dir =
cmSystemTools::GetFilenamePath(this-LocalGenerator-Convert(src,
Wojciech Migda wrote:
Hi again,
this workaround seems to do a trick:
in cmDependsC::WriteDependencies I've added a local variable to store
path to the source file being scanned for dependencies:
std::string root_dir =
cmSystemTools::GetFilenamePath(this-LocalGenerator-Convert(src,
On Sat, Mar 7, 2009 at 6:21 AM, Mike Arthur m...@mikearthur.co.uk wrote:
On Saturday 07 March 2009 11:08:43 Pau Garcia i Quiles wrote:
Whatever happened to this?
It's here:
http://code.google.com/p/cmakeports/
People are talking on the group list here and some stuff has been
committed.
In your top most CMakeLists.txt file you might want to try adding the
following:
# -- Setup output Directories -
SET (CMAKE_LIBRARY_OUTPUT_DIRECTORY
${PROJECT_BINARY_DIR}/Bin
CACHE PATH
Single Directory for all Libraries
)
# - Setup the
On Saturday 07 March 2009 20:45:55 Philip Lowman wrote:
I have no plans to develop a package manager from the work done in
CMakePorts. As I've stated in other mailing lists like sldev, I think that
would be a waste of time.
My apologies, rereading the messages that led me to draw that
12 matches
Mail list logo
