You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CMakeLists.txt
+5-3Lines changed: 5 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -14,6 +14,7 @@ option(SC_WITH_PHASE_CALLBACKS "Whether SystemC is built with simulation phase c
14
14
option(SC_WITH_PHASE_CALLBACK_TRACING"whether SystemC was build with phase callbacks for tracing. It needs to match the SystemC build configuration"OFF)
15
15
set(SCC_ARCHIVE_DIR_MODIFIER ""CACHESTRING"additional directory levels to store static library archives")
16
16
set(SCC_LIBRARY_DIR_MODIFIER ""CACHESTRING"additional directory levels to store libraries")
17
+
option(WITH_SCP4SCC"adds SCP compatibility layer for SCC, cannot be used together with a copy of SCP"OFF)
17
18
18
19
include(Common)
19
20
@@ -120,7 +121,7 @@ if (ENABLE_CLANG_TIDY)
120
121
endif()
121
122
endif()
122
123
123
-
find_package(Boost1.70REQUIREDCOMPONENTSsystemdate_time) # header only libraries must not be added here
124
+
find_package(BoostREQUIREDQUIETCOMPONENTSsystemdate_time) # header only libraries must not be added here
Copy file name to clipboardExpand all lines: README.md
+11-8Lines changed: 11 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,9 +15,9 @@ Here is a short list of features.
15
15
16
16
* Automatic tracer
17
17
18
-
The tracer(s) allow to automatically discover signals and sc_variables (see below) and register them with the trace file. If the configurer is being used the tracing can be controlled on an per-instance base
18
+
The tracer(s) allow to automatically discover signals and sc_variables (see below) and register them with the trace file. If the configurer is being used the tracing can be controlled on an per-instance base
19
19
20
-
* Various optimized trace file implementations
20
+
* Various optimized trace file implementations
21
21
* compressed VCD
22
22
* FST (used by [GTKWave](http://gtkwave.sourceforge.net/) and [Surfer](https://surfer-project.org/))
23
23
@@ -60,7 +60,7 @@ The full documentation can be found at the [Github pages](https://minres.github.
60
60
Build notes
61
61
=======================================
62
62
63
-
If SystemC is build using cmake with `SC_WITH_PHASE_CALLBACK_TRACING=ON` (which is the default for SystemC 2.3.4), tracing will not work. Either SystemC is being installed with SC_WITH_PHASE_CALLBACK_TRACING=ON (which is the prefered way as this setting is in sync with the automake configure configuration, see https://github.com/accellera-official/systemc/issues/24) or the SCC is being build using `SC_WITH_PHASE_CALLBACK_TRACING=ON`.
63
+
If SystemC is build using cmake with `SC_WITH_PHASE_CALLBACK_TRACING=ON` (which is the default for SystemC 2.3.4), tracing will not work. Either SystemC is being installed with SC_WITH_PHASE_CALLBACK_TRACING=ON (which is the prefered way as this setting is in sync with the automake configure configuration, see <https://github.com/accellera-official/systemc/issues/24>) or the SCC is being build using `SC_WITH_PHASE_CALLBACK_TRACING=ON`.
64
64
65
65
Build instructions using conan
66
66
=======================================
@@ -72,11 +72,11 @@ On Linux
72
72
73
73
The suggested build steps are:
74
74
75
-
- create a build directory and enter into it
76
-
- execute cmake with applicable options
77
-
- execute build
78
-
- install build
79
-
- run tests
75
+
* create a build directory and enter into it
76
+
* execute cmake with applicable options
77
+
* execute build
78
+
* install build
79
+
* run tests
80
80
81
81
For example:
82
82
@@ -91,6 +91,9 @@ For example:
91
91
92
92
```
93
93
94
+
> **_NOTE:_****Do not install SCC in the same installation directory as SystemC.**
95
+
SCC follows the convention of mapping C++ namespaces directly into the directory hierarchy. As many SCC components are related to TLM 2.0, a significant portion of the SCC code resides in the `tlm` namespace, which results in the creation of a `tlm` directory under SCC's `include` folder. The SystemC itself also provides a `tlm` header file (or directory) in its own include path. If SCC and SystemC are installed into the same prefix, this results in a clash to create a directory where a file or another directory already exists—causing installation errors. Install SCC and SystemC into separate directories.
0 commit comments