| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
As reported on the mailing list, find_path/file/library/program() basically don't work
at all if CMAKE_FIND_ROOT_PATH is set and searching in the host system directories
is disabled. This patch adds /include, /lib and /bin to the search directories, so they
will be appended to CMAKE_FIND_ROOT_PATH so this will work for the "Generic" platform (embedded
systems without OS)
Alex
|
| |
|
| |
|
| |
|
|
|
|
| |
This change depends on the fix for #9414 which should land very soon.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
The names are:
EABI: "ELF ARMEABI"
non-EABI: "ELF ARM"
Alex
|
|
|
|
| |
Alex
|
|
|
|
|
|
|
|
|
|
| |
(I accidentially removed ExternalProject.cmake from git by doing
mv ExternalProject.cmake ExternalProject.cmake.save
git checkout master
which I hoped would basically do a revert as it does with svn and cvs, but it
deleted the file from git)
Alex
|
|
|
|
|
| |
This is a feature request
--Eric
|
| |
|
|
|
|
| |
This reverts commit 108090fde96916ba666f035d1e260f036af5b31e.
|
|
|
|
|
|
|
| |
Detect the runtime linker's search path and add to the compile time
linker's search path. This is needed because OpenBSD's static linker
does not search for shared library dependencies in the same places as
the runtime linker.
|
|
|
|
|
|
| |
Patch from Brad Hards <bradh AT frogmouth DOT net>
Alex
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
The hook is called gp_resolved_file_type_override.
Signed-off-by: Michael Wild <themiwi@users.sourceforge.net>
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Teach compiler identification to support values such as
export CC='gcc -g -O2'
by separating the arguments on spaces. We already do this for the
values of CFLAGS, CXXFLAGS, and FFLAGS.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This allows the user not to link to the common libraries,
which are regularly required. The user must specify all
libraries that he does want to link in the find_package
line (png tiff jpeg zlib regex expat).
--HG--
extra : rebase_source : df29f96c957600629a34a1c5fafb8b3d6f274e22
|
| |
|
| |
|
| |
|
|
|
|
| |
Allow the user to set the CMake variable CTEST_COST_DATA_FILE, which will be used to store the cost data from test runs. If not set, defaults to the original location in the build tree Testing/Temporary dir.
|
|
|
|
|
|
|
|
| |
Commit "Modernize GNU compiler info on Windows" (2009-12-02) reorganized
GNU flags on Windows but let -fPIC slip through for compilation of
objects in shared libraries. While this flag is valid on most GNU
compiler platforms we need to suppress it in Windows-GNU.cmake just as
we already do in CYGWIN-GNU.cmake.
|
| |
|
| |
|
|
|
|
|
|
| |
This modifies the behavior of PYTHON_WRITE_MODULES_HEADER, should be backwards
compatible. Also marked a couple of the variables generated by adding Python
modules as advanced.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
PathScale Fortran mangles module symbols as "MY_SUB.in.MY_MODULE" and
also requires "my_module_" when the module is imported. We cannot
provide the symbol with ".in." mangling so we should not provide
"my_module_" because it would duplicate the one in the Fortran-provided
object file.
Commit "FortranCInterface: Fix PathScale detection" (2010-01-22) already
made the same fix for the non-underscore module case.
|
|
|
|
| |
compilers. Call it from all of the CMakeTesten_US.UTF-8Compiler.cmake files. In the message, print the full path to the tested compiler only for the Makefile generators. For Xcode and Visual Studio generators, print the generator instead so that users are not misled with the full path to a compiler that the generator may not even use. Xcode and Visual Studio have their own mechanisms for choosing the compiler to use during try_compile and build...
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the CTest module we previously warned if the source directory did not
contain known version control directories. The message was:
"CTest cannot determine repository type. Please set UPDATE_TYPE
to 'cvs' or 'svn'. CTest update will not work."
This was confusing when building sources from a tarball. Furthermore,
we now support many more version control tools. This feature is now
mature enough that the warning causes confusion more than it provides
real help. We simply remove it.
|
|
|
|
|
| |
The CTest module configures the command-line CTest dashboard mode.
We teach it to recognize .git directories.
|
|
|
|
|
| |
We use ELSEIF to simplify the cascading IF blocks for detecting version
control tools.
|
| |
|
|
|
|
| |
added a 3 second timeout when requesting the version from the server. Added an option to the CTestConfiguration that will be used to determine whether to query the version information at all. (Behavior for this setting is not yet defined.) Updated CMake's local CDash version setting to 1.6.
|
|
|
|
|
|
|
|
|
|
| |
The compiler documents symbols _DF_VERSION_ and _VF_VERSION_ but they do
not seem to be available to the preprocessor. Instead we add a vendor
query table entry for Compaq. Running "f90 -what" produces
Compaq Visual Fortran Optimizing Compiler Version ...
This clearly identifies the compiler.
|
|
|
|
|
|
|
| |
At least one Fortran compiler does not provide a preprocessor symbol to
identify itself. Instead we try running unknown compilers with version
query flags known for each vendor and look for known output. Future
commits will add vendor-specific flags/output table entries.
|
|
|
|
| |
always be the empty string. When the value of CMAKE_OSX_DEPLOYMENT_TARGET is the empty string, the -mmacosx-version-min flag should not show up on the compiler command line. The logic for selecting default value of CMAKE_OSX_SYSROOT is orthogonal to and independent of the value of the deployment target. The default value for CMAKE_OSX_SYSROOT is the SDK that corresponds to the current version of Mac OSX on which cmake is running.
|
|
|
|
| |
names.
|
|
|
|
| |
target properties.
|
| |
|