2011/12/9 Clifford Yapp cliffy...@gmail.com:
I decided to take a stab at using the Eclipse Unix Makefile generator
with my project - on import, I get the following error:
Error processing changed links in project description file.
No file system is defined for scheme: virtual
I'm not
On Fri, Dec 9, 2011 at 3:50 AM, Eric Noulard eric.noul...@gmail.com wrote:
2011/12/9 Clifford Yapp cliffy...@gmail.com:
I decided to take a stab at using the Eclipse Unix Makefile generator
with my project - on import, I get the following error:
Error processing changed links in project
Let's try replying to the list this time...
Eclipse 3.7.1 (Indigo) Eclipse succeeded in importing. I'm not sure how
to do a C/C++ project build with Eclipse (or that my build of Indigo
actually added everything it needed to) but it looks like the CMake
project import part of the equation
2.8.7rc1.
If you still have this problem, cmake probably didn't find Eclipse and so
could not detect the version.
For this case, you can now set CMAKE_ECLIPSE_VERSION to the version you have,
if you use cmake-gui to do this, you get a combobox to chose from.
Alex
--
Powered by www.kitware.com
Visit
I decided to take a stab at using the Eclipse Unix Makefile generator
with my project - on import, I get the following error:
Error processing changed links in project description file.
No file system is defined for scheme: virtual
I'm not really sure what this means or what issue it's
and put the Build_tree as a LinkedRessource
this is more or less the converse of what the Generator currently does.
1bis) If one wants to use CMake Eclipse CDT generator and
Eclipse Code Management to work he MUST do in-source built
i.e. CMAKE_BINARY_DIR==CMAKE_SOURCE_DIR
for generated files :))
I see 3 ways to go:
1) Stick to eclipse constraint and generate .project and .cproject
in the source tree and put the Build_tree as a LinkedRessource
this is more or less the converse of what the Generator currently does.
1bis) If one wants to use CMake Eclipse CDT
2007/8/2, Alexander Neundorf [EMAIL PROTECTED]:
On Thursday 02 August 2007 05:34, Eric Noulard wrote:
Moreover I think in-source built should be supported by the CDT Generator
in order to be consistent with other generator.
[...]
Yes, in-source builds should work and having Eclipse
for generated files :))
I see 3 ways to go:
1) Stick to eclipse constraint and generate .project and .cproject
in the source tree and put the Build_tree as a LinkedRessource
this is more or less the converse of what the Generator
currently does.
1bis) If one wants to use CMake Eclipse CDT
does.
1bis) If one wants to use CMake Eclipse CDT generator and
Eclipse Code Management to work he MUST do in-source built
i.e. CMAKE_BINARY_DIR==CMAKE_SOURCE_DIR
In this case the CDT Generator should be modified
in order to detect if it has been called
. Not that I know any better way to do
it.. ;-)
What do you mean with I make a change to my project ?
A change to the cmake files or a change in Eclipse ?
What kind of things can you change about the project inside Eclipse which
cmake can't handle ?
Maybe the existing project files could be parsed
products.
Setup of debugging seemed more straight forward. Right click the
executable and Debug local Application
Just some observations on how I personally use eclipse and cmake. YMMV.
--
Mike Jackson Senior Research Engineer
Innovative Management Technology Services
cvs/team interaction and the out-of-source
project for development. You would have:
workspace - ~/eclipse
|
-- CMake - cvs source checkout, ~/eclipse/CMake
|
-- cmake_bin - out-of-source build in ~/eclipse/cmake_bin
that links to ~/eclipse/CMake sources
|
-- cmake_bin2
and work
around the limitations available so that the user doesn't see them.
The idea is to have stable, *easily reproducible* sessions with
Eclipse.
Just some observations on how I personally use eclipse and cmake. YMMV.
I certainly appreciate these and they have helped me understand some
Miguel A. Figueroa-Villanueva wrote:
1. integration with the Microsoft tools.
Bill mentioned that we can compile with the VS Express (or any VS
version) compiler and debug with cygwin gdb, right? Can somebody point
me in the direction on how to do this? I seem to recall that it wasn't
with the
to the source as usual. Use the
CVS project to manage cvs/team interaction and the out-of-source
project for development. You would have:
workspace - ~/eclipse
|
-- CMake - cvs source checkout, ~/eclipse/CMake
|
-- cmake_bin - out-of-source build in ~/eclipse/cmake_bin
2007/8/2, Mike Jackson [EMAIL PROTECTED]:
On Aug 2, 2007, at 10:39 AM, Eric Noulard wrote:
When using out-of-source build with CMake
(including Visual Studio) the project file is generated in the
Build Tree
not the Source Tree.
LIke I said, Eclipse is NOT like other IDEs and therefor
2007/7/31, Miguel A. Figueroa-Villanueva [EMAIL PROTECTED]:
Attached is the file. I changed some variable names and other minor
things, but I'm not certain it follows all the coding standards. I
leave that to your inspection, although please point out whatever you
find that you needed to fix
2007/8/1, Eric Noulard [EMAIL PROTECTED]:
2007/7/31, Miguel A. Figueroa-Villanueva [EMAIL PROTECTED]:
Attached is the file. I changed some variable names and other minor
things, but I'm not certain it follows all the coding standards. I
leave that to your inspection, although please point
On 8/1/07, Eric Noulard wrote:
2007/7/31, Miguel A. Figueroa-Villanueva:
Attached is the file. I changed some variable names and other minor
things, but I'm not certain it follows all the coding standards. I
leave that to your inspection, although please point out whatever you
find that
On 8/1/07, Eric Noulard wrote:
2007/8/1, Eric Noulard :
2007/7/31, Miguel A. Figueroa-Villanueva :
I have somes remarks:
1) The referred sources for the build are a cvs checkout
but they do not appear as such in Eclipse,
i.e. the Team menu is not enabled. :((
May be the CVS
On Wednesday 01 August 2007 07:56, Miguel A. Figueroa-Villanueva wrote:
On 8/1/07, Eric Noulard wrote:
...
I've tried to manually activate Team menu on this
particular folder but I am still unable to do it without
Sharing the whole project which is definitely not what
I want since
type2/type
locationD:/path/to/P2/location
/link
/linkedResources
...
and I also put the following in the .cproject:
...
pathentry kind=src path=P1/
pathentry kind=src path=P2/
...
It's not as good as encapsulating each cmake project
==
I will think if we can hack something regarding this Eclipse Team restriction,
I will file a feature wish on platform-cvs-dev as well
refering to the current CMake Eclipse CDT work as a motivation.
--
Erk
___
CMake mailing list
CMake
On 7/31/07, Alexander Neundorf wrote:
On Tuesday 31 July 2007 09:51, you wrote:
...
Great! If you personally think this is good and can review/apply the
patches relatively quickly then that will work well for me. What I was
worried about was that I open a feature request and,
Hi Miguel,
On Tuesday 31 July 2007 13:42, Miguel A. Figueroa-Villanueva wrote:
On 7/31/07, Alexander Neundorf wrote:
On Tuesday 31 July 2007 09:51, you wrote:
...
Great! If you personally think this is good and can review/apply the
patches relatively quickly then that will work well
Alexander Neundorf wrote:
Hi Miguel,
.
.
.
The indentation is not completely correct:
if (!fout) { return; }
Hello,
Are there any cindent settings to do auto-indenting for the coding
standards?
Regards,
Juan
Alexander Neundorf wrote:
Hi Miguel,
On Tuesday 31 July 2007 13:42, Miguel
what
I was last editing so no problem the second time around. Second, I
don't double-click the project file created by cmake to open eclipse.
I open eclipse, then I have to import the Existing Eclipse Project
to my workspace. That is done once then eclipse remembers, of course.
For the KDevelop
On Tuesday 31 July 2007 15:40, you wrote:
On 7/31/07, Alexander Neundorf [EMAIL PROTECTED] wrote:
...
How do you handle the cmake projects ? You iterate over the map, which
effect does this have ?
Well, since I want to create the .project/.cproject in the
CMAKE_BINARY_DIR what I did was
You dont. That is what I tried to explain in one of my other posts.
Eclipse has the notion of One project PER top level directory. If you
had a project setup like the above then you would have to actually
take the folder sub1 and place it at the same level as foo.
Let's get straight
On Tuesday 31 July 2007 16:24, Mike Jackson wrote:
You dont. That is what I tried to explain in one of my other posts.
Eclipse has the notion of One project PER top level directory. If you
had a project setup like the above then you would have to actually
take the folder sub1 and place it at
--
Mike Jackson Senior Research Engineer
Innovative Management Technology Services
On Jul 31, 2007, at 4:40 PM, Alexander Neundorf wrote:
On Tuesday 31 July 2007 16:24, Mike Jackson wrote:
You dont. That is what I tried to explain in one of my other posts.
Eclipse has the notion of
On 7/31/07, Alexander Neundorf [EMAIL PROTECTED] wrote:
On Tuesday 31 July 2007 16:24, Mike Jackson wrote:
You dont. That is what I tried to explain in one of my other posts.
Eclipse has the notion of One project PER top level directory. If you
had a project setup like the above then you
path=P1/
pathentry kind=src path=P2/
...
It's not as good as encapsulating each cmake project in an eclipse
project, but that is just not supported right now in eclipse cdt as
you stated.
Include Dirs: Loop through them and add them all, regardless of
where they are defined. Eclipse needs them
34 matches
Mail list logo
