POIDE will no longer allow me to have project result files in folders below the ppj folder...
The attachment is pretty self-explanatory... this is new with 7.00 RC3...
If I manually edit the POC_PROJECT_RESULTDIR to read ..# or ..\# it works just fine. It's just the wizard won't let me do it...
The desired file tree is like this...
AllProjects --- workspace1 --- project1 --- output
... source.c
=== project1.ppj
--- project2 --- output
... source.c
... resources.rc
=== project2.ppj
... project1.exe
... project2.dll
=== workspace1.ppw
I used to do this all the time with 5.0 and 6.0 with no problems at all. For reasons wholly unclear version 7 just won't do it.
Maybe PellesC ide needs File menu option to create New Workspace ?
File -> New -> Workspace
BTW:
If you first create empty workspace/project and add new projects folders below it,
maybe that works. You can remove that empty project when the first real project is created.
Name: TestPrj
Location: C:\code\PellesC\TestPrj
Output: C:\code\PellesC\TestPrj\output
Result: C:\code\PellesC\TestPrj
Create new workspace
Name: project1
Location: C:\code\PellesC\TestPrj\project1
Output: C:\code\PellesC\TestPrj\project1\output
Result: C:\code\PellesC\TestPrj\project1\..
Add to existing workspace
Name: project2
Location: C:\code\PellesC\TestPrj\project2
Output: C:\code\PellesC\TestPrj\project2\output
Result: C:\code\PellesC\TestPrj\project2\..
Add to existing workspace
Quote from: timovjl on June 16, 2012, 11:11:40 AM
Maybe PellesC ide needs File menu option to create New Workspace ?
File -> New -> Workspace
Exactly what it needs....
The problem is that workspaces are a side effect of creating projects, the ppw file is then stuffed into the folder with one of the project files.... But if you look at
this thread (http://forum.pellesc.de/index.php?topic=4547.msg17139#msg17139) you will see that is not how we organize our work... We want to build projects inside a workspace.
Following your lead it would be something like this...
Workspace root = d:\Code
File -> New -> Workspace ...
Name: skyhook
ppw = d:\code\skyhook\skyhook.ppw
File -> New -> Project
Name : server
ppj = d:\code\skyhook\server\server.ppj
Location: d:\code\skyhook\server
Output: d:\code\skyhook\server\output
Result: d:\code\skyhook\
The reason I want the Result pointing at the workspace folder is that when I have multiple projects I can use that folder to get all the EXEs, DLLs etc all into one place for testing.
It has always been awkward to arrange this structure, but now, short of manually editing the ppj files, it's impossible. If I open one of my older projects with this structure, POIDE can edit, compile, build, even rebuild the workspace with no problems... it's that cursed wizard thats the problem.
Here's a couple of captures from one of my project "workspaces"... the first is the workspace itself, the second is the RMRemote folder within the workspace... the source, ppj fles, etc are all in the folders within the workspace, the runtimes are all in the workspace folder itself. As it should be.
How about a global output folder below the workspace where each project points to?
Quote from: Stefan Pendl on June 16, 2012, 09:00:48 PM
How about a global output folder below the workspace where each project points to?
Won't work... The wizard demands that the result folder points inside each project folder.
You should be able to point the result folder *anywhere*. POIDE proper does this... it's the wizard blocking it... It never used to...
Try this... modify a "hello world" project so that it's result folder points to a completely different hard drive or partition... you will also have to change the build chain at the bottom... but the various tools and POIDE itself will work with it... I took a project on D:\c-code\test and set it's result directory to j:\ which is a flash drive, and it worked.
Quote from: Stefan Pendl on June 16, 2012, 09:00:48 PM
How about a global output folder below the workspace where each project points to?
There are so many different preferences. The ide should not restrict the user in this.
Quote from: CommonTater on June 16, 2012, 09:47:47 PMWon't work... The wizard demands that the result folder points inside each project folder.
One way would be to create a hard link of the output folder in the workspace to one inside of each project folder using the Hardlink Shell Extension (http://schinagl.priv.at/nt/hardlinkshellext/hardlinkshellext.html).
This would be a nice workaround.
Quote from: Stefan Pendl on June 16, 2012, 10:20:04 PM
Quote from: CommonTater on June 16, 2012, 09:47:47 PMWon't work... The wizard demands that the result folder points inside each project folder.
One way would be to create a hard link of the output folder in the workspace to one inside of each project folder using the Hardlink Shell Extension (http://schinagl.priv.at/nt/hardlinkshellext/hardlinkshellext.html).
This would be a nice workaround.
Stephan... thanks for the suggestions but it's just the wizard... I can manually edit the project files in notepad and get what I want. It's just that I shouldn't have to and didn't have to until this latest version.
I'm far more concerned about the foul up with the resource editor... This I need to use every day.
UPDATE: Just tried this with 650 rc4 and 700 rc2... works fine both places.
Ok... temporary fix for this problem... Install 7.00 rc2... copy POIDE out of the Bin folder to a safe place... Install 7.00 rc3 (to get the compiler fixes, etc.) copy the RC2 version of POIDE into the Bin folder.
Not Fixed in 700 RC4.... >:(