News:

The new Release 25.03 is out! You can download binaries for Windows and many major Linux distros here .

Main Menu

small bug report

Started by huzhongshan, August 11, 2010, 02:03:46 AM

Previous topic - Next topic
Print
Go Down Pages1
User actions

huzhongshan

August 11, 2010, 02:03:46 AM
version 10.05 , winxp

when there two projects in workspace , one is project a , the other is project b . prj a 's build target is debug , the prj b is set to release. If I choose bulid project b , when project b IS compiling , I double click project a , It seems when project b compiled completely , project a build target changes to release .

ollydbg

#1
August 11, 2010, 02:15:44 AM
Quote from: huzhongshan on August 11, 2010, 02:03:46 AM
version 10.05 , winxp

when there two projects in workspace , one is project a , the other is project b . prj a 's build target is debug , the prj b is set to release. If I choose bulid project b , when project b IS compiling , I double click project a , It seems when project b compiled completely , project a build target changes to release .

So, you mean: we should forbid the switch b to a, when b is under compiling.
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

huzhongshan

#2
August 11, 2010, 06:43:13 AM
maybe , this method is a solution.
when switch change from a to b , the b's config. should not be changed ( change to a 's build target config).

Jenna

#3
August 11, 2010, 09:21:24 AM
It does not happen here.
What happens, is that if b depends on a  and you build b and a gets automatically build, it uses the same build target, that is active in b.
Print
Go Up Pages1
User actions