User forums > Help

minor issues about cbp file

(1/3) > >>

Freem:
I recently have setup a project at savannah.nongnu.org.
Here, an admin told that cbp file should have license in it, like source files. (I never thought about adding a license in a project file, by the way!)

So I tried to add-it, and verify if a change in C::B will let it in the file, but C::B remove it.

This is a very minor issue, or maybe an improvement idea, but it could be interesting if C::B could just modify sections it have to modify.
Another more minor issue (a PEBCAK one in fact) is that if there is a broke in the project file (like plain text out of markup) C::B will not load it, but will not say why or even if it have loaded it.

Those 2 problems are in the latest nightly.

And at last, and totally out of topic, I tried to use C::B with MS Visual Studio 2008 at work (I just can't use efficiently an IDE which can't highlight text similar to the selected one, or is so messy with project options. This is the point which made me remember how user friendly is C::B!). It work nice, but I have found that there is an encoding issue when debugging (debug with GDB).
The nightly used is 7452 if I remember correctly...

Alpha:
I have another minor issue: when using a dynamic library, there are options to create a custom name for the import library and the definition file.  Any changes made here work during the active session, however, they are not saved in the cbp.


--- Quote from: Freem on December 02, 2011, 12:09:10 am ---I recently have setup a project at savannah.nongnu.org.
Here, an admin told that cbp file should have license in it, like source files. (I never thought about adding a license in a project file, by the way!)

So I tried to add-it, and verify if a change in C::B will let it in the file, but C::B remove it.

This is a very minor issue, or maybe an improvement idea, but it could be interesting if C::B could just modify sections it have to modify.

--- End quote ---
Another option would be to have Code::Blocks store any xml comments (<!-- text -->) during the opening of a workspace/project file; then on save, write all stored comments to the top of the respective files.  (File format would be left backwards-compatible.)

ollydbg:

--- Quote from: Freem on December 02, 2011, 12:09:10 am ---And at last, and totally out of topic, I tried to use C::B with MS Visual Studio 2008 at work (I just can't use efficiently an IDE which can't highlight text similar to the selected one, or is so messy with project options. This is the point which made me remember how user friendly is C::B!). It work nice, but I have found that there is an encoding issue when debugging (debug with GDB).
The nightly used is 7452 if I remember correctly...

--- End quote ---
Which encoding issue? Can you be more specific?


--- Quote from: Freem on December 02, 2011, 12:09:10 am ---I recently have setup a project at savannah.nongnu.org.
Here, an admin told that cbp file should have license in it, like source files. (I never thought about adding a license in a project file, by the way!)
So I tried to add-it, and verify if a change in C::B will let it in the file, but C::B remove it.

--- End quote ---
I think C::B's cbp file have a "notes" page, you can see it in Right click on your cbp project->Context menu->Properties..->Notes.
So, you can put the license there. :D

oBFusCATed:
Or you can use some of your time to provide a patch for setting the license, I doubt it will take you much time :)

MortenMacFly:
I wonder how they handle Visual Studio project files - this should be the same problem. Are you sure the guys understood that this is a project file and not a source file?

In the mean time: You can surely use the project notes to add a license as "work-around". This will persists across savings.

Navigation

[0] Message Index

[#] Next page