User forums > Nightly builds

The 15 august 2006 build is out.

<< < (2/2)

Jewe:
Wxsmith still hangs.

Hi got a 1,2,3 reproduction of the problem.

1. open new project wx
2. close the project./ C::B
3. open C::B and project again
4. select yes on the import info to file
5. add a Notebook to a dialog.

result ==> C::B 100% cpu time.

test was done on a winXp sp2 machine

Jewe:
Additional "feature",

a control is losing all of its settings while its moved in the tree structure.
is this a "known" issue?

regards,

Jewe

reptils:

--- Quote from: MortenMacFly on August 16, 2006, 10:46:36 am ---If you ask a question in the forum please do a search before. This question has been answered many times: Creating a Makefile has been disabled (it still is available in RC2 though) due to the changes that have been done and will be done to the build system. Once this work is finished the Makefile generation will be re-attached (and overworked).
Anyway, please notice that Makefiles are much less powerful and result in slower creation in addition compared to C::B. Why would you use Makefiles if you have C::B?! ;-)
With regards, Morten.

--- End quote ---
thanks for your answer,
I don't use Makefile explicitly with make.exe, I just need makefile sometime to see exectaly if I toke the good options, good path etc... But you are right I use C::B to avoid problems with makefile.

mandrav:

--- Quote from: reptils on August 16, 2006, 01:28:44 pm ---
--- Quote from: MortenMacFly on August 16, 2006, 10:46:36 am ---If you ask a question in the forum please do a search before. This question has been answered many times: Creating a Makefile has been disabled (it still is available in RC2 though) due to the changes that have been done and will be done to the build system. Once this work is finished the Makefile generation will be re-attached (and overworked).
Anyway, please notice that Makefiles are much less powerful and result in slower creation in addition compared to C::B. Why would you use Makefiles if you have C::B?! ;-)
With regards, Morten.

--- End quote ---
thanks for your answer,
I don't use Makefile explicitly with make.exe, I just need makefile sometime to see exectaly if I toke the good options, good path etc... But you are right I use C::B to avoid problems with makefile.

--- End quote ---

Well, makefiles are usable for example when you want to give your project to someone who doesn't have Code::Blocks yet (why? ;)).
That's why this functionality will probably be back (not in the near future though).

If all you want to do is check the options C::B passes to the compiler/linker, just follow the path in Morten's signature...

rcoll:

--- Quote from: mandrav on August 16, 2006, 01:38:19 pm ---
Well, makefiles are usable for example when you want to give your project to someone who doesn't have Code::Blocks yet (why? ;)).
That's why this functionality will probably be back (not in the near future though).

If all you want to do is check the options C::B passes to the compiler/linker, just follow the path in Morten's signature...

--- End quote ---

Actually, in my business the long-establish rule is that every piece of code that goes into version
control must have a makefile with it. regarless of whether we actually use the makefile or not.
Some brainiac higher up the food chain than I decided long ago that makefiles would be the company
standard for re-creating a product or family of products.

-- Ron --

Navigation

[0] Message Index

[*] Previous page