Comments (11)
Some ideas for information that would be useful:
- if on Linux: some of the output of
lsb_release -a
- if on *nix: some of the output of
uname -a
- CMake version
- git version (?)
- checksum of last git commit (?)
- Compiler version (always, even if already cached by CMake)
- ROOT version (always)
- libFTDI/libFTD2XX versions
from pxar.
Hi Hanno,
the version of the checked out code must be part of the dump that cmake
produces (imvho).
If possible, also whether the following packages are installed:
- glibc-devel.i_, libc6-dev-i_, glibc-devel-*
- g++-multilib, libstdc++-devel.i*
and what the value of the env vars
- LIBRARY_PATH
- C_INCLUDE_PATH
- CPLUS_INCLUDE_PATH
is (or better yet: the complete result of printenv). (see e.g.
http://stackoverflow.com/questions/7412548/gnu-stubs-32-h-no-such-file-or-directorywhich
I found useful)
Also: is it possible to skip producing the documentation targets if no
LaTeX is installed and just finish the Makefiles nevertheless? I realized
that I cannot even compile anything without LaTeX installed (without
mutilating the CMAKE file).
I think that there will be lab computers where no LaTeX/doxygen is or needs
to be installed.
Cheers,
--U.
On Wed, Jan 15, 2014 at 1:05 PM, hperrey [email protected] wrote:
Some ideas for information that would be useful:
- if on Linux: some of the output of lsb_release -a
- if on *nix: some of the output of uname -a
- CMake version
- git version (?)
- checksum of last git commit (?)
- Compiler version (always, even if already cached by CMake)
- ROOT version (always)
- libFTDI/libFTD2XX versions
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/31#issuecomment-32355858
.
from pxar.
last git commit is already printed:
-- Determined API version v0.0.2+1~g651a6e7.
which means it is 1 commit after the tag v0.0.2, and that commit has the hash being 651a6e7
- pointing directly to the commit checked out last.
However, this is only updated when running cmake ..
, not after git pull; make install;
.
from pxar.
concerning caching: I wouldn't fight with CMake's cache but tell the users to do
cd build/
rm -rf *
cmake ..
before even attempting to ask any question. Because not having a clean build folder is 80% of the failures already.
from pxar.
Most other information we can select from the list here:
http://cmake.org/Wiki/CMake_Useful_Variables#System_.26_Compiler_Information
...and just print them.
from pxar.
Most of the really useful information is now in the CMake output; I would prefer not to include e.g. environment variables as this would seriously blow up the amount of console output and would make it more difficult to spot errors/warnings.
The presence of devel packages should already be checked by CMake (or we need to add those checks, but that is not part of this particular issue imho).
I will close this issue now -- please reopen if you think some important information is still missing from the output.
from pxar.
Came to my mind while chatting with Urs at coffee: git version and checksum of last git commit will likely not be available if somebody installs the software downloading a tarball from github (an option users later will liekly do who don't want to use git for whatever reason). Should this case be handled somehow or not?
from pxar.
Simon's CMake code takes care of that: if the .git
directory is missing (as it would be when installed via tar ball) the version string in the CMake file is used instead.
from pxar.
Yes. So the only thing we have to think of is to update that version number once we tag a new release. I just realize that I already forgot that for v0.2.0 - sorry...
from pxar.
Done, bumper version to v0.2.1 and update CMakeLists.txt acordingly. New tag there.
from pxar.
Perfect. Thanks.
from pxar.
Related Issues (20)
- Unable to measure hitmap in Xray tests with Pxar master branch and FW 4.4 HOT 8
- unphysical scurve thresholds when plateau not found HOT 3
- inconsisten tbmParameter file naming for L1 modules HOT 2
- specify position of gui window HOT 6
- proc600v2 not correctly supported
- Possible Conflict with Scientific Linux 6.8 HOT 11
- Trimming failure for some pixels due to failure of fit HOT 1
- Critical readout error for layer 1 modules HOT 7
- Read out errors in L2 X-ray tests with master/4.7 HOT 3
- vsh is a 4 bit dac for proc600 HOT 2
- DTB clock and pXar APIs ... HOT 2
- Retrieve pixel pulse height ... HOT 5
- Issue with core/CMakeLists.txt HOT 1
- PHOptimization flawed with current chip (PROC600v3) HOT 1
- Trigger timeout truncated to 8 bit (pxarCore)
- Improve the timing scans for TBM10 (layer 1) HOT 1
- Implement the fix to configure modules with less noise. Urgent! HOT 1
- PH optimisation for PROC600 HOT 1
- cmake fixes
- Search for DTBs fails if other FTDI devices are present HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pxar.