Eclipse Community Forums: C / C++ IDE (CDT) » 2019-12 copy / paste project won't "run"

Home » Language IDEs » C / C++ IDE (CDT) » 2019-12 copy / paste project won't "run"

2019-12 copy / paste project won't "run" [message #1819307]

Sun, 12 January 2020 20:33

Eclipse User

After clean install of 2019-12 I am unable to find why copy/ paste project won't "run".
It only does "Launching..." , it generally shows 45% as last value, then nothing.
On 2019-09 I checked "Terminate and relaunch..." at it worked just fine,
On 2010-12 has no effect on "run" , and "Launching..." is much faster when NOT selected.

The original project imported to new 2019-12 workspace goes thru "launching..." , little slower then 2019-09 did, but "runs" normally.

I did check the workspace, tried different workspace and had same results.

I cannot go back to 2019-09 so I need to find solution or option of 2019-12 I have missed.
In the meantime I have to make backup of my current running project - outside Eclipse.
Sort of back-pedalling.

Re: 2019-12 copy / paste project won't "run" [message #1819323 is a reply to message #1819307]

Mon, 13 January 2020 03:05

Eclipse User

By "copy/ paste " I assume you meant you copied the project directory; pasted it into the workspace; and renamed it.
That doesn't work.
If you used the OS to do this, all you've done is made a duplicate copy of the files in the project directory.
But those files will still contain references to the old directory.

If you used the Eclipse Project view to "copy and paste" then only the project name will be changed.
But the "new" (copied) project files will still contain references to the old directory.

An example.
I used Eclipse to copy and paste project "HelloEigen" to "CopyEigen".
But, as the following greps show, only the project name was changed.

"HelloEigen" can still be found in CopyEigen files

[dvavra@fred Default]$ pwd
/home/dvavra/workspaces/2019-09/Default

[dvavra@fred Default]$ find CopyEigen -type f -print0 | xargs -0 grep -l "HelloEigen"
CopyEigen/Debug/makefile
CopyEigen/Debug/src/HelloEigen.d
CopyEigen/Debug/src/subdir.mk
CopyEigen/Debug/src/HelloEigen.o
CopyEigen/.cproject
CopyEigen/src/HelloEigen.cpp

[dvavra@fred Default]$ find CopyEigen -type f -print0 | xargs -0 grep -l "CopyEigen"
CopyEigen/.project

There are still paths and references to "HelloEigen" in the CopyEigen project

[dvavra@fred Default]$ grep -n "HelloEigen" CopyEigen/.cproject
23:							<builder buildPath="${workspace_loc:/HelloEigen}/Debug" id="cdt.managedbuild.builder.gnu.cross.1332758920" keepEnvironmentInBuildfile="false" name="Gnu Make Builder" superClass="cdt.managedbuild.builder.gnu.cross"/>
74:							<builder buildPath="${workspace_loc:/HelloEigen}/Release" id="cdt.managedbuild.target.gnu.builder.exe.release.1648277706" keepEnvironmentInBuildfile="false" managedBuildOn="true" name="Gnu Make Builder" superClass="cdt.managedbuild.target.gnu.builder.exe.release"/>
107:		<project id="HelloEigen.cdt.managedbuild.target.gnu.exe.2014715158" name="Executable" projectType="cdt.managedbuild.target.gnu.exe"/>

[dvavra@fred Default]$ grep -n "CopyEigen" CopyEigen/.project
3:	<name>CopyEigen</name>

Remember this? https://www.eclipse.org/forums/index.php?t=msg&th=1101875&goto=1818911&#msg_1818911
Quote:

I use rsync to migrate a workspace from one release set to another.
Unfortunately, there are absolute paths within a lot of the files pointing to the old location.
...
Requires a massive edit to fix. ("sed -i" can help here)

A similar problem occurs when renaming a workspace.
There are files with references to the old name.

[Updated on: Mon, 13 January 2020 10:39] by Moderator

Re: 2019-12 copy / paste project won't "run" [message #1819412 is a reply to message #1819323]

Tue, 14 January 2020 13:12

Eclipse User

Huh?
In my Eclipse I have been copying / pasting , including "project" , since first use.
Standard usage actually ads "serial number" to new project name, from "test" to "test1" and builds new directory structure in same workspace.
No renaming is necessary , but optional.

Are we talking about same things?

But for some unknown reason (?) - after I created "new" and copied a test project - it now works.
New moon (eclipse ) ??

[Updated on: Tue, 14 January 2020 13:13] by Moderator

Re: 2019-12 copy / paste project won't "run" [message #1819417 is a reply to message #1819412]

Tue, 14 January 2020 14:25

Eclipse User

Quote:

Standard usage actually ads "serial number" to new project name, from "test" to "test1"
No renaming is necessary , but optional.

You can't have two project with the same name in a workspace.
That means when copying and pasting one you must give it another name.
So, renaming IS necessary.
It's irrelevant how the new name is determined.

Quote:

Are we talking about same things?

Apparently not.
You will have better success in getting help if your posts are more informative.

Quote:

after I created "new" and copied a test project - it now works

What "new" did you create?
Not at all clear what you did but glad it worked for you.

[Updated on: Tue, 14 January 2020 15:00] by Moderator

Previous Topic:	ARM packages update error Eclipse C/C++
Next Topic:	Debug is not working in Eclipse Photon

Goto Forum:

-=] Back to Top [=-

Current Time: Mon Jun 23 19:12:46 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter