I have two projects, one depends on the other, and when I ask Eclipse to clean the dependent project, it cleans both of them. Is there a way to disable this behavior?
It is worth noting that on building the dependent project eclipse also builds both of them.
I have tried already:
Clean up Eclipse Build Order
Remove the dependency in Project Properties -> C/C++ General -> Paths and Symbols -> References
Related
Let's make an example in Eclipse: I have two different source files for a Startup with a main-function, but depending on which build configuration I use, either one of them is used, or the other one.
I do this, by defining a custom symbol with the "-d" option in one of the build configurations, and leaving it out in the other one.
#ifdef CUSTOMSYMBOL
...
Specifically, under Eclipse, I can edit these settings under Project -> Properties -> C/C++ Build -> Settings -> Cygwin C++ Compiler -> Prepocessor
(I am using Cygwin under Windows for my C++ projects)
This works. Depending on which build configuration I use, only one of the two source files will be built by the compiler and the other one will be ignored.
However, this setting is specific to Cygwin.
I can't figure out, how to do it in QNX Momentics, since I do not have those options under the qcc Compiler.
You can do this in the Compiler Tab of your QNX C/C++ Project as shown below:
I've a C++ project in eclipse which is version managed with git. I've a git submodule, which is another project I've written in C++. The submodule has its main function and my project has its own.
Eclipse chooses other main (from the submodule) to compile when I press build. Is there a way to choose which main to build in eclipse?
Update: I'm still working on the issue. Excluding resources from the project didn't help either. Will answer the question when I solve it.
Update 2: Solved at last. See my answer.
I have solved the problem, at last. The solution is not a simple and straightforward one, so I'm writing step by step:
First set your toolchain correctly from Properties -> C/C++ Build -> Tool Chain Editor -> Current toolchain. It's MacOSX GCCor Linux GCC for me.
Set your correct project source path. I've symlinked the files from projects I imported as submodules to my project, so setting the correct source directory didn't exclude any required files from my project. Setting is at Properties -> C/C++ General -> Paths & Symbols -> Source Location. Make sure you exclude the other submodules and symlink the required files to your project.
Change the name of the artifact (binary, library, etc.) to something different than the ${projName}, because when you have submodules, you will have a directory named as ${projName} inside your build folder. Setting is at Properties -> C/C++ Build -> Settings -> Build Artifact -> Artifact name.
After making these changes, your project should build automatically. Looks like eclipse makes all necessary checks during build, but doesn't warn you about the problems. I had to see all these problems with running make --always-build inside the Debug folder.
I have locally forked (via hg clone) a C/C++ (Eclipse CDT) project and imported it into my Eclipse workspace. My editor window for the forked project now looks like this:
Clearly, these are not real errors, since the code builds correctly. Also, these errors are not marked in the original project from which this one was forked.
Why does Eclipse think there are errors in this source?
EDIT: Eclipse error messages when hovering over the "bugs" are, e.g., Type int64_t could not be resolved and symbol 'cout' could not be resolved.
EDIT: I've noticed that Eclipse usually shows a "folder" named includes in the project. It is missing for this project. How can I get it back?
Eclipse has to know the paths where to find the include files. This may be set using general eclipse settings or project by project.
For some reason it seems like the default paths are not set for your current project.
What you can do:
Open the project settings and go to C/C++ General -> Paths and Symbols (at least that is how it is called in my eclipse version) and fix the include directories.
Maybe it is enough to load the default configuration for that specific project. Maybe you have to set up your include pathes by yourself. On Unix / OS X this should usually be usr/include. On Windows I have no idea, but that should be easy to find out.
Afterwards it may be necessary that your rebuild your eclipse index (right click on your project, then index -> rebuild).
If that does not help please share a screenshot of the Paths and Symbols dialog of your project.
Also see the eclipse documentation on this topic.
I had to include
CDT Cross GCC Built-in Compiler Settings
CDT GCC Built in Compiler Settings [ Shared ]
in Properties for the project -> C/C++ General -> Preprocessor Include Paths, Macros etc. -> Providers
add this define in Eclipse to Project Properties->C/C++ General->Paths and Symbols
__STDC_FORMAT_MACROS
Rebuild your eclipse index. It will work.
This worked on Mac OS X Yosemite 10.10.5, Eclipse version Mars.1 Release (4.5.1):
Since the includes are usually discovered by Eclipse through the toolchain, check that you have an actual toolchain set (when I ran into this problem after importing a project, the toolchain was set to "No toolchain."):
Project -> Properties -> C/C++ Build -> Tool Chain Editor -> Current toolchain
If no toolchains appear in the dropdown, try unchecking "Display compatible toolchains only" and choosing a toolchain (I chose Cross GCC). When I saved the changes and re-opened the project properties to look at this field again, "Display compatible toolchains only" was automatically re-checked.
Then re-index the project:
Project -> C/C++ Index -> Rebuild
This solved the problem for me (the "pseudo-errors" disappeared, and the includes "folder" appeared under my project in the file system view).
Have you #included the correct files in your code? For std::cout it would be:
#include <iostream>
and for int64_t:
#include stdint.h
Create a new solution with a C++ console command-line project
Create a new project, a C++ static library
Make the command-line project depend on the library
Make sure "Link Library Dependencies" is turned on in Configuration => Linker => General (it is by default)
Visual Studio will still not link the library.
How can I fix this? It worked in Visual Studio 2008.
This still works, but was changed in VS 2010:
"With VS2010, we stopped supporting project dependencies defining implicit references and we also introduced a new way of defining project dependencies at the project level. Since a project reference and a project dependency are close concepts, both applying to a project, it made sense to have them represented together, in a consistent way, in the project file. As you will see in the snippets below, the only difference between a project reference definition and a project dependency definition consists in metadata that defines the output assembly inclusion/exclusion into/from the main project link command line.
Although we did not remove the “Project Dependencies” dialog, we recommend defining new project dependencies via the “Framework and References” dialog. You need to set the “Reference Assembly Output” property in the property page UI to false for a project dependency and to true for a project reference."
Just right-click on the console project, select "Properties->Common Properties->Framework and References->Add New Reference" and add the static library project; also check that "Link Library Dependencies" is True on the right hand side. Seems to work for debug and release builds. You learn something new every day. ;)
They changed the UI for adding C++ project dependencies in VS2010, but oddly enough, without removing the old UI, or in any way indicating that it no longer works.
To create the dependency in VS2010, you need to use "Add New Reference" (can be found in project properties), and maybe also in the project's right-click menu (don't have VS here to check)
The old "Project Dependencies" dialog is basically broken now.
For MSVC 14 (2015 version) right-click on the project, then "Add->Reference..." and check all the needed dependencies.
Yes, it has changed somewhere between 2010 and 2015 versions. Fun!
And if you are looking to link a project that has resources in it - you need to specify the .res file directly in the list of linker input dependencies (project's properties dialog box) as it doesn't get picked up by the above configuration.
UPDATE
Still the same (new) behavior in MSVC 2017
I believe the old UI (dependencies) affects build order for Visual Studio, when building from within the IDE, for info. The new project configuration system embeds the references in each project file so that you can build from outside the IDE (whereas in previous versions, you could not, because you would not get automatic linking for dependencies, since dependencies were only done at the solution level).
There are also some issues with more complex projects in the new system; specifically, all resulting binary projects need to have explicit references to every dependent library to build correctly, whereas previously they could be effectively inherited from other dependent libraries. Same underlying cause, though.
I don't understand what is exactly a builder in CDT, and what is the relationship with the "C/C++ Build" content.
I set up SCons in the "C/C++ Build" confuguration. It does work : I made two configurations (release and debug), and my SCons scripts are launched. But as I try now to debug, I am studying these Builders stauuf (I am discovering Eclipse...).
The documentation is not clear at all about this point.
Thanks for help.
I'm not exactly sure what your problem is, but I'll try to explain how builders work.
Any Eclipse project has zero or more builders, and they are invoked (in order) when Eclipse builds a project. There are different kinds of builders which do different things, such as invoking an external build tool or validating an XML file. You can define your own builders if you want.
A CDT project typically has two builders. The first one is the CDT builder which is responsible for compiling your code. If you are using an external build tool you are most likely using a "makefile project", in which case the CDT builder simply invokes your build tool for you. This is by default called "make", but you can change it in the project settings.
The second builder is the "scanner discovery" builder. The purpose of this builder is to try to figure out which include paths etc. to use for the indexer so that auto-completion will work, etc. If you are using an external tool, chances are that you will need to set up these yourself under the "Paths and Symbols" tab.
Builders are in general not involved when debugging, but you may run into trouble if the build system doesn't put the compiled binaries in a place where CDT expects. There should be a tab in the project properties where you can configure how/where CDT looks for binaries.