|Related to : Let build.sbt define dependency on another local library|
|matrix library: inline vs define|
Use the inline keyword. There are several disadvantages if you use the
preprocessor to develop function-like macros:
no type safety checking
no sanity checking
bad to debug
expressions passed to macros can be evaluated more than once
|Maven -- how to find out all library dependency on parent pom|
There is no easy way to do this because parent pom's are handled
differently than maven dependencies. So dependency:tree won't work.
What you can try doing though is pull each dependency and their pom,
parse through and check the parent. You may also try pulling up the
effective pom and use it to parse through.
|How to add library dependency additionally for exact plugin during execution?|
Add the it to libraryDependenies in projects/build.sbt and it should
The reason is that sbt is recursive, so PROJECT_DIR/build.sbt defines
stuff together with project/*.scala build files, and project/*.sbt are
in the same way defining settings for project/project - the project
that builds the project.
You can read more about that here:
|Where are the dependency libraries defined in the build.gradle file downloaded?|
Gradle's dependency cache is located under ~/.gradle/caches.
(Inspecting the dependencies of the generated IntelliJ project will
reveal that.) The exact cache layout is unspecified, and may change
between Gradle versions.
|How to build a compiler-independent C++ library (for Solaris Studio and gcc)?|
Your plan is correct.
As long as your library exposes a C API compatible with platform ABI
(sizes and alignments of C types, calling conventions) and does not
throw C++ exceptions you are not going to have troubles linking your
library using other compilers or languages.
You could also add a C++ header only wrapper for your C API to make it
easily reusable from C++ and exception safe.