Re: [CMake] Building ROOT into Geant4 Application
Mr. Odera,
On Wed, Dec 6, 2017 at 2:40 PM, Dim, Odera U wrote:
> Hi CMake Experts,
>
>
> Please I use CMake to build my Geant4 applications with no issues. However,
> recently I needed to build ROOT into my Geant4 application for the purpose
> of extracting and processing simulation data. I have followed the many
> instructions which exist online both on the Genat4 and ROOT sides but none
> seems to produce the required results. The issue i'm having I believe is
> related to the linkage of both Geant4 and ROOT libraries top the generated
> executable during compilation. I am able to configure and generate build
> files with a CMakeLists with no errors. Compilation also seems to also
> complete with no errors but when I run the application I get an error which
> specifies that LLVM are exposed to Cling and so I need to hide them. In my
> CMakeLists (which I can provide to you) I do not explicitly link Cling to my
> executable all I do is link the executable to ROOT libraries
> (${ROOT_LIBRARIES}). Please, could you help me with this issue or do you
> know a way that I could link libraries and not expose LLVM to Cling? Thank
> you.
>
Can you provide the text of the errors as they are given? Are you
experiencing build errors, or are you wanting to quiet runtime
messages?
Which OS are you compiling and running on? Which build instructions
are you following? What are the build commands that you ran? Are you
using Clang, and is it necessary that you use Clang?
If we can't resolve your problem here it is possible I can refer you
to someone off-list, but I am not entirely sure what difficulty you
are having.
Cheers,
R0b0t1
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
[CMake] Building ROOT into Geant4 Application
Hi CMake Experts,
Please I use CMake to build my Geant4 applications with no issues. However,
recently I needed to build ROOT into my Geant4 application for the purpose of
extracting and processing simulation data. I have followed the many
instructions which exist online both on the Genat4 and ROOT sides but none
seems to produce the required results. The issue i'm having I believe is
related to the linkage of both Geant4 and ROOT libraries top the generated
executable during compilation. I am able to configure and generate build files
with a CMakeLists with no errors. Compilation also seems to also complete with
no errors but when I run the application I get an error which specifies that
LLVM are exposed to Cling and so I need to hide them. In my CMakeLists (which I
can provide to you) I do not explicitly link Cling to my executable all I do is
link the executable to ROOT libraries (${ROOT_LIBRARIES}). Please, could you
help me with this issue or do you know a way that I could link libraries and
not expose LLVM to Cling? Thank you.
Dim Odera
UMass Lowell
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
[CMake] CMake 3.10 adding mystery source file to target?
I just tried to configure our project with CMake 3.10 and got some errors. The same project configures fine with CMake 3.8.x and 3.9.x as evidenced here (http://my.cdash.org/index.php?project=DREAM3D). I get an error about a Qt5 qrc generated file not being found. -- Configuring done CMake Error in /Users/mjackson/Workspace/DREAM3D_Plugins/AskNDEToolbox/Applications/ScanViewer/CMakeLists.txt: Cannot find source file: /Users/mjackson/Workspace/DREAM3D-Build/3.10/Plugins/AskNDEToolbox/qrc_AskNDEToolbox.cpp Tried extensions .c .C .c++ .cc .cpp .cxx .m .M .mm .h .hh .h++ .hm .hpp .hxx .in .txx -- Generating done -- Build files have been written to: /Users/mjackson/Workspace/DREAM3D-Build/3.10 But the issue is that if I actually print out all the source files for the " ScanViewer " taget, "qrc_AskNDEToolbox.cpp" NEVER shows up? There is another target that uses that file but NOT ScanViewer. I am also getting some errors on the same project but on Windows (the previous was on macOS Sierra) where some of our plugins that get configured all of a sudden cannot find some of their files. I have not tried on Linux x64 yet to figure out if anything is broken on that side. Thanks for any information anyone may have. Thoughts. Ideas. All are welcome. -- Michael Jackson | Owner, President BlueQuartz Software [e] mike.jack...@bluequartz.net [w] www.bluequartz.net -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] [CMAKE] - custom compiler for Android
HI Brad,
Thank you for the response
However we want more guidance on how do we start with the changes needed for
the compiler support
To be more clear, we are trying to build support for the embarcadero
compilers bccaarm.exe. To give more insight on the work and our query, we
have attached a working toolchain that we created and works fine with CMAKE
and the compiler. But we have given the system name CMAKE_SYSTEM_NAME as
"_Android"
Since we havent given it as "Android", it reads all the libraries and the
compilers from our toolchain file and gives the desired output.
Can you please give us some guidance to achieve the same with
CMAKE_SYSTEM_NAME as "Android"
Thanks & Regards,
Ramya
-Original Message-
From: Brad King [mailto:brad.k...@kitware.com]
Sent: Wednesday, December 06, 2017 1:24 AM
To: ramya.gopalkris...@accoliteindia.com
Cc: CMake@cmake.org; 'Sumit Chourasia'
Subject: Re: [CMAKE] - custom compiler for Android
On 12/05/2017 12:05 PM, ramya.gopalkris...@accoliteindia.com wrote:
> Please validate our current understanding when a toolchain file or
> command-line option sets CMAKE_SYSTEM_NAME to "Android"
You may find this note helpful:
https://gitlab.kitware.com/cmake/cmake/issues/16708#note_300971
> Ideally, we want our toolchain file to tell cmake the libraries to
> include/link and the compilers to use.
Toolchain files can set the path to compilers on the host, but
target-platform-wide information like the set of libraries and include
directories to use typically belongs in platform information modules (e.g.
`Platform/Android-...` and the like).
> But once, System has been determined as android, cmake goes through
> the above sequence of events and expects toolchains to be specified
> for either clang, gcc or llvm compilers.
We try to support the compilers that come with the NDK out of the box.
More work may be needed to support other compilers, just as would be the
case for any new platform or new compiler.
> Determine-Compiler-NDK.cmake - We would need to add support for an
> "NewCompiler Toolchain" which would contain android libraries and
compilers.
Since your compiler doesn't come with the NDK, perhaps you could look at
using the standalone toolchain mode.
> New Android-{NewCompiler}-C.cmake, Android-{ NewCompiler }-CXX.cmake,
> Android-{ NewCompiler }.cmake and another appropriate toolchain file
> to set target architecture and compiler flags.
If you have some new compiler then something like that would be needed.
This would be the case for a new compiler on any platform.
-Brad
bccaarm.cmake
Description: Binary data
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
