心得技巧

html5 HTML/Xhtml CSS XML/XSLT Dreamweaver教程 Frontpage教程心得技巧

上一篇: 常见数据结构下一篇:Unsafe应用解析

Setting up SystemC and Eclipse for C++ hardware simulation

发布时间：2022-06-25 发布网站：脚本宝典

脚本宝典收集整理的这篇文章主要介绍了Setting up SystemC and Eclipse for C++ hardware simulation，脚本宝典觉得挺不错的，现在分享给大家，也给大家做个参考。

https://karibe.co.ke/2014/02/setting-up-Systemc-and-eclipse-for-c-hardware-simulation/

browse: Home / 2014 / February / Setting up SystemC and Eclipse for C++ hardware simulation

Setting up SystemC and Eclipse for C++ hardware simulation

By Karibe on February 21, 2014

This post was updated on 26th APRil,2018 for the latest systemc release: version 2.3.2. This is a step by step guide to setting up systemc library based on an edIT of instructions that come with the source and configuring and running an eclipse-iDE C++ Project. As of now (April 2018), systemc-2.3.2 is the most recent systemc version. It provides several improvements over systemc-2.3.1, including bug fixes and several new features that are disabled by default. On this post, we will be installing systemc2.3.2 “as is” without enabling any new experimental features, for learning purposes.

1. May the source be with you

There are two ways to get the source: First and easiest is cloning the github repository Get into the source/dev’t directory

cd ~/src/git

clone the repo

git clone https://github.COM/Muriukidavid/systemc-2.3.2.git

Get into the systemC source directory, ready to build.

cd systemc-2.3.2

Second method is getting the latest From the develoPEr commUnity: To get the source code from accellera systems, you need to head to the download page and download the latest version of the library. Place and Extract the source in your home folder and cd there

cd systemc-2.3.2

2. pre-requisites

Most Linux installations have the required tools by default, just make sure you have make installed. If not, install it:

sudo apt-get install build-essential automake liBTool

To check that you have these already, use the which command:

which g++

Then you have to set some environmental VARiables:

export CXX=g++

If you have a custom compiled gcc, you have the /usr/local/bin/gcc and its g++ as default compiler, probably an older version for building something, then you need to be more specific with the system installed gcc path like so:

export CXX=/usr/bin/g++
export CC=/usr/bin/gcc

Then create a working directory, where you will build the library before installing it

mkdir objdir

get into that directory

cd objdir

3. configuring

Run autoreconf command in the base directory to prepare for configuration, check for dependancies according to the system you have.

../autoreconf -f -i

Create a folder where the installation will be made under /usr/local

sudo mkdir /usr/local/systemc-2.3.2

While at ‘objdir’ folder, run the command

../configure --prefix=/usr/local/systemc-2.3.2

This configures the installation folder and generates the makefiles, among other things…. Last few lines output:

configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating src/systemc.pc
config.status: creating src/tlm.pc
config.status: creating src/sysc/Makefile
config.status: creating src/sysc/packages/boost/Makefile
config.status: creating src/sysc/packages/qt/Makefile
config.status: creating src/tlm_core/Makefile
config.status: creating src/tlm_utils/Makefile
config.status: creating examples/Makefile
config.status: creating examples/sysc/Makefile
config.status: creating examples/tlm/Makefile
config.status: creating examples/tlm/common/Makefile
config.status: creating docs/Makefile
config.status: creating docs/sysc/doxygen/Doxyfile
config.status: creating docs/tlm/doxygen/Doxyfile
config.status: executing depfiles commands
config.status: executing libtool commands
---------------------------------------------------------------------
Configuration summary of SystemC 2.3.2 for x86_64-unknown-linux-gnu
---------------------------------------------------------------------

 Directory SETUP (based on classic layout):
   Installation prefix (aka SYSTEMC_HOME):
      /usr/local/systemc-2.3.2
   Header files  : /include
   Libraries     : /lib-linux64
   Documentation : /docs
   Examples      : /examples

 Architecture    : linux64
 Compiler        : /usr/bin/g++ (C/C++)
 
 Build settings:
   Enable compiler optimizations  : yes
   Include debugging symbols      : no
   Coroutine package for processes: QuickThreads
   Enable VCD scopes by default   : yes
   Disable async_request_update   : no
   Phase callbacks (experimental) : no
 
---------------------------------------------------------------------

4. make the library

Assuming configuration went on finishing smoothly, build the library

make

If you want it to run faster, make use of multiple threads with the -j option, I used

make -j4

5. Install the library in your system

sudo make install

After this command, you can check that the library was properly installed:

ls /usr/local/systemc-2.3.2/lib-linux64/
libsystemc-2.3.2.so  libsystemc.a  libsystemc.la  libsystemc.so  pkgconfig

Note: for a 32-bit system, the library folder is /usr/local/systemc-2.3.2/lib-linux/. you can type while using tab to auto-complete paths

To configure the library with the standard Linux library path, which will ease up linking stage of project build:

sudo ln -s /usr/local/systemc-2.3.2/lib-linux64/libsystemc-2.3.2.so /usr/lib/libsystemc-2.3.2.so

You can check the path is correct:

ls -l /usr/lib/libsystemc-2.3.2.so 
lrwxrwxrwx 1 root root 56 Apr 26 12:31 /usr/lib/libsystemc-2.3.2.so -> /usr/local/systemc-2.3.2/lib-linux64/libsystemc-2.3.2.so

This library path problem has of late been persistent and the solution is to add a config file under /etc/ld.so.conf.d/ as follows:

sudo gedit /etc/ld.so.conf.d/systemc.conf

add the path information to that file, i.e “/usr/local/systemc-2.3.2/lib-linux/” or “/usr/local/systemc-2.3.2/lib-linux64/” depending on your system. then run

sudo ldconfig

6. Get Eclipse

If you already have eclipse, go to step 7. If not, go to Eclipse.org and download the Eclipse IDE for C/C++ developers. Choose 32-bit/64-bit Linux version and the closest mirror… Extract under the home folder and optionally set up a .desktop shortcut