Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

Breakpoints layout saving

<< < (2/2)

Bat:
One point is that my usage is a bit different from legacy desktop app compiled in C++. So I do not say at all this can be good for trunk.
At the time, we commit .cbp file, this is ok. I've in my head 2 issues that I haven't track for now (between git, merge, C::B) :
-We sometimes loose "current target" that is resetted to default target.
-Pre and post process build command line are sometimes duplicated after editing project
-Part of debug configuration are lost

Things are a bit more complicated for workspace. It's our usage that differ from C::B general usage.

In fact, in our usage, we need to commit (so isolated in one or more files) :
-a list of project with relative path to each others (can be see a kind of 'super project' or 'sub workspace')
-a dependancy list between theses projects
-some targets definition, program arguments, debug configuration

I haven't enought time to investigate 'best' global solution, so I continue to add some smalls extensions to macro, project loader, ...

oBFusCATed:

--- Quote from: Bat on October 16, 2016, 12:15:59 pm ----We sometimes loose "current target" that is resetted to default target.

--- End quote ---
I don't think this is stored in the project.


--- Quote from: Bat on October 16, 2016, 12:15:59 pm ----Pre and post process build command line are sometimes duplicated after editing project
-Part of debug configuration are lost

--- End quote ---
Post bug reports for these when you know the steps to reproduce them.


--- Quote from: Bat on October 16, 2016, 12:15:59 pm ---I haven't enought time to investigate 'best' global solution, so I continue to add some smalls extensions to macro, project loader, ...

--- End quote ---
The global solution to this is probably to use scripting to load and setup the projects.

Navigation

[0] Message Index

[*] Previous page