User forums > Nightly builds

The 09 November 2015 build (10561) is out.

<< < (3/3)

cacb:

--- Quote from: jens on December 12, 2015, 03:47:08 pm ---You can download it again, the tarball is fixed.
But it never had the correct revision. The correct revision is in the appropriate "*.debian.tar.gz"-file. You have to download it and unpack it inside the codeblocks-folder from the "*.orig.tar.gz"-file.

--- End quote ---

Thank you very much, that was quick! I tried replacing the whole "debian" folder from the "*.debian.tar.gz" in the extracted codeblocks-folder, but then the build failed. However it worked to only replace the debian/changelog file and edit the debian/rules as before (to compile against wx2.8 ). Then the result was *.deb files with proper revision numbers & also the same displayed in C::B. It seems to work just fine.

cacb:
Merry Christmas everyone!

Just a quick note on something I have seen in the Windows version of this 09 November 2015 build (10561) build:

When I close a workspace (workspace A) using "File->Close Workspace" and open another (workspace B), typically via the "Recent projects" links on the C::B front page, I find that my post build steps are sometimes not working properly. Below is an example specification of a post build step:

$(CPDE_USR)\bin\cpde_usr  -bin -xi -project=$(PROJECT_NAME)  -root=$(PROJECT_DIR)  -build=$(TARGET_NAME)  -target=$(TARGET_OUTPUT_FILE)  -usr=$(CPDE_USR)

(CPDE_USR is a C::B environment variable I have defined, it isn't a problem here. )

The problem is that sometimes the $(PROJECT_NAME), $(PROJECT_DIR), $(TARGET_NAME)  etc. variables of C::B keep their settings from the used-to-be-current project in the recently closed workspace A, i.e. they are NOT reassigned to the actually-current project in workspace B.

The work-around when this happens is to close/restart C::B and open workspace B, then all is fine in the build. Note that no changes have occurred in workspace B.


I am able to reproduce on my own workspaces like this:
1. Open C:B
2. Open Workspace A, Rebuild All
3. File -> Cose Workspace
4. Open Workspace B by clicking link on front page
5. Rebuild all. Post-build step fails here, indicating the $(PROJECT_NAME) is the used-to-be project in the previous workspace A

cacb:

--- Quote from: cacb on December 24, 2015, 12:16:49 pm ---I am able to reproduce on my own workspaces like this:
1. Open C:B
2. Open Workspace A, Rebuild All
3. File -> Cose Workspace
4. Open Workspace B by clicking link on front page
5. Rebuild all. Post-build step fails here, indicating the $(PROJECT_NAME) is the used-to-be project in the previous workspace A

--- End quote ---

I have just confirmed that the exact same problem occurs under Linux, built from Jens' tarball (svn 10621).

oBFusCATed:
Please post a ticket on sf.net so we can track this problem and probably fix it.

cacb:

--- Quote from: oBFusCATed on December 28, 2015, 02:09:28 pm ---Please post a ticket on sf.net so we can track this problem and probably fix it.

--- End quote ---

Done: ticket #277

Navigation

[0] Message Index

[*] Previous page