| View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0007273 | CMake | CMake | public | 2008-07-02 14:45 | 2016-06-10 14:30 | ||||
| Reporter | R Wackerbarth | ||||||||
| Assigned To | Bill Hoffman | ||||||||
| Priority | normal | Severity | feature | Reproducibility | N/A | ||||
| Status | closed | Resolution | moved | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | CMake-2-6 | ||||||||
| Target Version | Fixed in Version | ||||||||
| Summary | 0007273: Provide Access to more System Information | ||||||||
| Description | CTest provides significantly more information about the test machine than it used to provide. For example, it now provides the processor speed and available memory in addition to the OSName, OSVersion, Hostname, etc. The older parameters are available at build configuration time as CMAKE_SYSTEM_NAME, etc. It would be useful to have the additional info available. In particular, ProcessorClockFrequency and AvailablePhysicalMemory are examples that affect the"default" configuration of my desired builds. I also have different implementations of (time) critical routines and would like to have the correct one selected to match the processor. | ||||||||
| Additional Information | See kwsys::SystemInformation for available info that could be exported to CMAKE variables. | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files | |||||||||
| Relationships | |
| Relationships |
| Notes | |
|
(0012598) Bill Hoffman (manager) 2008-07-02 14:53 |
Where/how do you see these variables passed back to the tests? Can you give me a use case with some sample code? |
|
(0012601) R Wackerbarth (reporter) 2008-07-02 15:43 |
I see them passed back the the CMake configuration. Just as I now have IF (${CMAKE_SYSTEM_NAME} MATCHES "Linux") SET(SourceFiles ${SourceFiles} LinuxHandlers.c) ENDIF (${CMAKE_SYSTEM_NAME} MATCHES "Linux") I might add IF(${CMAKE_PHYSICAL_MEMORY} GREATER 1023) ADD_TEST(TestLargeSample MyProgram -tablesize=1000000 testdata) ENDIF(${CMAKE_PHYSICAL_MEMORY} GREATER 1023) because I know that the program cannot "malloc" the large table in a machine without adequate memory |
|
(0041436) Kitware Robot (administrator) 2016-06-10 14:27 |
Resolving issue as `moved`. This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page. |
| Notes |
| Issue History | |||
| Date Modified | Username | Field | Change |
| 2008-07-02 14:45 | R Wackerbarth | New Issue | |
| 2008-07-02 14:53 | Bill Hoffman | Note Added: 0012598 | |
| 2008-07-02 15:43 | R Wackerbarth | Note Added: 0012601 | |
| 2008-08-19 17:22 | Bill Hoffman | Status | new => assigned |
| 2008-08-19 17:22 | Bill Hoffman | Assigned To | => Bill Hoffman |
| 2016-06-10 14:27 | Kitware Robot | Note Added: 0041436 | |
| 2016-06-10 14:27 | Kitware Robot | Status | assigned => resolved |
| 2016-06-10 14:27 | Kitware Robot | Resolution | open => moved |
| 2016-06-10 14:30 | Kitware Robot | Status | resolved => closed |
| Issue History |
| Copyright © 2000 - 2018 MantisBT Team |