I'm a Coverity user, and I want to scan the DPDK project as below.
(https://scan.coverity.com/projects/dpdk-data-plane-development-kit)
I did a scan on a DPDK project, which is able to build with build command as below,
"make config T=x86_64-native-linuxapp-gcc && make T=x86_64-native-linuxapp-gcc ".
Then I got " No files were emitted to analyze"! (( --gcc is configured !))
After a discussion with Official Support, he recommended here to us.
Because there's high probability that Make command calls another build tool, or run gcc compile command with container.
So we want to know if we could learn how DPDK build project.
Does DPDK uses docker?
We already have a environment could build DPDK project.
What is the cov-build command I can uses?
Thanks,
BR,
Hardy
Related
In one of our projects we have used Gstreamer good plugins. I see that each element has a Makefile for building.
Now I wanted to upgrade rtpmanager code (https://github.com/GStreamer/gst-plugins-good/tree/master/gst/rtpmanager) inside Gstreamer. But, I see that there are no Makfiles anymore but 'meson.build' file.
Currently our project build does not support meson. So, is there a way to convert the latest rtpmanager code involving meson.build to traditional Makefile kind of build so that I can integrate its latest changes into my project.
Meson does not and never will generate makefiles.
Qemu meson PoC is using a tool to convert ninja files to Makefile:
https://github.com/bonzini/qemu/blob/meson-poc/scripts/ninjatool.py
I am debugging an open source golang web project
https://github.com/studygolang/studygolang
Use the build command in the documentation "make build" and "make start",and then the project running.
The problem is when I modify some code，How to recompile the project。
I try “make reload”,but it not work. how to do ?
Simply run make build again. You can read the Makefile located in the base directory of the project to learn what it does.
I followed the example https://github.com/lasote/conan-gtest-example to add GTest to my project via conan. Moreoever I followed these instructions https://docs.conan.io/en/latest/integrations/ide/clion.html to set up conan within CLion.
The two samples work as expected. But I cannot get CLion pick up the files under "test_package" when I follow both instructions. How can I set up CLion correctly to work with my test_package by using conan?
Thanks
It's not possible using that plugin.
The Clion plugin is able to run conan install under the hood.
You can take a look on Clion's blog post about how to integrate both tools.
The idea is creating a plugin to solve your dependencies for C++ project, not a shortcut when creating Conan packages.
If you want to build that package and testing it, you should run:
conan create . soccertrash/testing
The command above will export, install, build and test your package. To learn more about, you can read the docs here.
To request a new feature, as your mentioned before, you can open a new request for Conan team here.
Regards!
How can I build a Linux kernel in Travis CI. I have added script: make menuconfig to my Travis config and it doesn't work and says
No output has been received in the last 10 minutes
How can I fix this?
Link to GitHub repo : https://github.com/ProjectPolyester/tegra_kernel and submit fixes in PRs if possible
Travis monitors your build process and if there is no output for about 10 minutes, it assumes that your process is stuck somewhere for unknown reasons, and then kills it.
Solution in your case :
You need to provide with the actual build command.
make menuconfig
actually just allows you to configure the kernel. It doesn't really starts the kernel build process. So there is no output of this command.
Also, the kernel should already be configured or you can download the appropriate .config file if its available some where online. And then there will be no need to execute:
make menuconfig
The build command
It can be simply
make
or something like
make -j3 modules ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- LOCALVERSION=-$SOURCE_VERSION
The second one is actually to perform cross compilation.
You also need to set all the prerequisites like downloading the header file etc
You may want to take a look at this script , it crosscompiles the modules only, not the entire kernel.
If you want to use the old config for a new kernel, you can use make olddefconfig. Here is my example how to compile and boot a new kernel in travis: https://github.com/avagin/criu/blob/linux-next/scripts/travis/kexec.sh#L54
I know that this is an old thread but I was recently able to get Travis CI working on building a Linux kernel
https://github.com/GlassROM-devices/android_kernel_oneplus_msm8994/commit/6ed484812bbd4a25c3b22e730b7489eaaf668da1
GCC fix is for toolchains compiled on Debian unstable, arch, gentoo, etc. These toolchains will fail to compile on Ubuntu so you'll have to use the GCC fix for these toolchains
And you really want to upgrade GCC before you even try building a kernel. Travis CI has a very old GCC that will fail if you try to compile the kernel
In my commit I'm building it with GCC 8 linaro built by myself
I'm developing a C++ application in Code::Blocks.
My program has a few dependencies and has to run under Linux and Windows, this is why
I use Code::Blocks.
Now I'd like to include Travis CI for testing the builds.
On the Travis server, where I have no X11, I won't be able to run Code::Blocks. How can I build my project without Code::Blocks. (Is there a possibility to create "a Makefile" out of the .cbp-file?
This page (Code::Blocks Wiki) mentions there is a --build flag, but you need Code::Blocks & X11. Is there a server way without X11?
You can not run anything which require X11 on Travis, and as far as I know, there is no way to launch a build using Code::Blocks without requiring X11.
The best choice would be to set up your project differently, for example using a Makefile. You will be able to configure Code::Blocks to use your Makefile and also to build on Travis using the make command.
You can also consider using CMake (especially if you are not familiar with Makefile syntax, but not only). This will let you configure your project in a more high level way (compared to a Makefile), and then you will be able to generate a Makefile or a project for the IDE of your choice.
I used cbp2make (C::B Forum entry).
It is quite simple
cbp2make -in project.cbp -out Makefile
and it worked immediatly, even with a more complex configuration
than a simple command line project in Code::Blocks.
It also generates the same build targets as in Code::Blocks. For example make Release would work.
The debian package list shows only a few dependencies, so X11 is not required.