9e76e7a321
The current protoc_action generates declarations that impose the requirement for .proto files to import from the BUILDDIR. This prevents .proto files to import themselves relative to their own directory. For example, if there are two files build/pkg/a.proto and build/pkg/b.proto, and b.proto imports a.proto, it must do so as "import pkg/a.proto", as opposed to "import a.proto"; otherwise, the generated declaration will give rise to a compilation error. This is a problem for EXTRAS where .proto files are gem5-independent, so they cannot import from gem5's build directory. An example is https://github.com/ARM-software/ATP-Engine This commit changes the protoc_action so that declarations are generated relative to the SOURCE directory. This enables .proto files to import other .proto files within the same directory. Note it is not possible to import other .proto files in different directories, but support for it is not currently necessary. More details on the proto path: https://developers.google.com/protocol-buffers/docs/reference/cpp-generated#invocation Related: https://gem5-review.googlesource.com/c/public/gem5/+/55903 Change-Id: Ib3e67ae817f8ad0b6803c90d23469267eff16178 Signed-off-by: Adrián Herrera Arcila <adrian.herrera@arm.com> Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/64491 Reviewed-by: Jason Lowe-Power <power.jg@gmail.com> Tested-by: kokoro <noreply+kokoro@google.com> Maintainer: Jason Lowe-Power <power.jg@gmail.com>
This is the gem5 simulator. The main website can be found at http://www.gem5.org A good starting point is http://www.gem5.org/about, and for more information about building the simulator and getting started please see http://www.gem5.org/documentation and http://www.gem5.org/documentation/learning_gem5/introduction. To build gem5, you will need the following software: g++ or clang, Python (gem5 links in the Python interpreter), SCons, zlib, m4, and lastly protobuf if you want trace capture and playback support. Please see http://www.gem5.org/documentation/general_docs/building for more details concerning the minimum versions of these tools. Once you have all dependencies resolved, type 'scons build/<CONFIG>/gem5.opt' where CONFIG is one of the options in build_opts like ARM, NULL, MIPS, POWER, SPARC, X86, Garnet_standalone, etc. This will build an optimized version of the gem5 binary (gem5.opt) with the the specified configuration. See http://www.gem5.org/documentation/general_docs/building for more details and options. The main source tree includes these subdirectories: - build_opts: pre-made default configurations for gem5 - build_tools: tools used internally by gem5's build process. - configs: example simulation configuration scripts - ext: less-common external packages needed to build gem5 - include: include files for use in other programs - site_scons: modular components of the build system - src: source code of the gem5 simulator - system: source for some optional system software for simulated systems - tests: regression tests - util: useful utility programs and files To run full-system simulations, you may need compiled system firmware, kernel binaries and one or more disk images, depending on gem5's configuration and what type of workload you're trying to run. Many of those resources can be downloaded from http://resources.gem5.org, and/or from the git repository here: https://gem5.googlesource.com/public/gem5-resources/ If you have questions, please send mail to gem5-users@gem5.org Enjoy using gem5 and please share your modifications and extensions.