Author Topic: A note about the Windows builds  (Read 16910 times)

Offline tiwag

  • Developer
  • Lives here!
  • *****
  • Posts: 1196
  • sailing away ...
    • tiwag.cb
Re: A note about the Windows builds
« Reply #15 on: December 22, 2005, 10:21:04 pm »
These are the current settings...

this ok now, but it can be as it is since a few days only ... for month it contained the bogus gcc_dll/msw in the linker section.
anyway, good that this was cleaned...

but seriously - take a closer look in the templates and pugins/contrib/* directories
there you can see that the usage of WX_CFG is totally mixed and that's confusing

finally : @thomas - thanks for cleaning the current situation !

Offline thomas

  • Administrator
  • Lives here!
  • *****
  • Posts: 3979
Re: A note about the Windows builds
« Reply #16 on: December 22, 2005, 10:29:27 pm »
this ok now, but it can be as it is since a few days only ...
About 2 days, 23 hours  :)


explain it please !
After changing global user variables, it will make sense to change the Code::Blocks projects. I think it would be unnecessarily complicated to change them now and then again in a few days (supposed I ever find out how to add a wxGrid to that darn dialog without getting an exception...).
For the moment, the project file works, so I would not touch it unless necessary.
"We should forget about small efficiencies, say about 97% of the time: Premature quotation is the root of public humiliation."

Offline takeshi miya

  • Lives here!
  • ****
  • Posts: 1487
Re: A note about the Windows builds
« Reply #17 on: December 23, 2005, 09:40:47 am »
I don't know for what you'll be using wxGrid, but you could try with another simmilar like wxListCtrl, or wxProperyGrid.

Offline thomas

  • Administrator
  • Lives here!
  • *****
  • Posts: 3979
Re: A note about the Windows builds
« Reply #18 on: December 23, 2005, 01:32:33 pm »
I don't know for what you'll be using wxGrid, but you could try with another simmilar like wxListCtrl, or wxProperyGrid.
Actually wxPropertyGrid is *exactly* what I need, I looked at that, too. But since it is not a part of wxWidgets, that would mean adding another third party library to the build just for one dialog. And it would still have to be added manually, you can't just put it into the XRC file.
wxListCtrl only displays one column, so it is not usable for that purpose (except with yet another dialog for every edit).
"We should forget about small efficiencies, say about 97% of the time: Premature quotation is the root of public humiliation."

Offline 280Z28

  • Regular
  • ***
  • Posts: 397
  • *insert unicode here*
Re: A note about the Windows builds
« Reply #19 on: December 23, 2005, 02:28:51 pm »
I don't know for what you'll be using wxGrid, but you could try with another simmilar like wxListCtrl, or wxProperyGrid.
Actually wxPropertyGrid is *exactly* what I need, I looked at that, too. But since it is not a part of wxWidgets, that would mean adding another third party library to the build just for one dialog. And it would still have to be added manually, you can't just put it into the XRC file.
wxListCtrl only displays one column, so it is not usable for that purpose (except with yet another dialog for every edit).

wxPropertyGrid is already in the source as part of wxSmith. You could move that folder to the sdk folder or something? Just a random idea :)
78 280Z, "a few bolt-ons" - [email protected]
99 Trans Am, "Daily Driver" - 525rwhp/475rwtq
 Check out The Sam Zone :cool:

Offline thomas

  • Administrator
  • Lives here!
  • *****
  • Posts: 3979
Re: A note about the Windows builds
« Reply #20 on: December 23, 2005, 02:52:07 pm »
Might be worth a consideration, if that doesn't break stuff.
"We should forget about small efficiencies, say about 97% of the time: Premature quotation is the root of public humiliation."

Offline 280Z28

  • Regular
  • ***
  • Posts: 397
  • *insert unicode here*
Re: A note about the Windows builds
« Reply #21 on: December 23, 2005, 03:34:48 pm »
Might be worth a consideration, if that doesn't break stuff.

Just make a copy of it in svn for now, and then tell (wxSmith's maintainer) to remove the copy from the wxSmith folder once he's updated his project to point to the copy you made. :)
78 280Z, "a few bolt-ons" - [email protected]
99 Trans Am, "Daily Driver" - 525rwhp/475rwtq
 Check out The Sam Zone :cool:

Offline takeshi miya

  • Lives here!
  • ****
  • Posts: 1487
Re: A note about the Windows builds
« Reply #22 on: December 23, 2005, 07:58:44 pm »
I would say that would be really good, because wxPropertyGrid in some other parts of C::B will do a very good job (like in the Compiler flags, separated by categories, and so on).

Offline thomas

  • Administrator
  • Lives here!
  • *****
  • Posts: 3979
Re: A note about the Windows builds
« Reply #23 on: December 23, 2005, 08:11:16 pm »
Afraid it will not... at least not as it looks right now. When added to the panel, it produces really nasty drawing errors, and it has the same resizing problem as wxGrid. Worse yet, it shows in 16x16 unless you explicitely give a fixed size... If you specify the dialog as the property grid's parent (instead of a panel), it draws really fine, albeit over all other controls, and not in the correct place either...

Maybe you are not thought to manually add items to a XRC created dialog at all (although I cannot think of a reason not to), or maybe I just don't know how to do it properly... either way, it does not work as easily as one would expect. The compiler flags dialog is created from XRC too, so it will have the same problem.
"We should forget about small efficiencies, say about 97% of the time: Premature quotation is the root of public humiliation."

Offline takeshi miya

  • Lives here!
  • ****
  • Posts: 1487
Re: A note about the Windows builds
« Reply #24 on: December 23, 2005, 08:29:46 pm »
 :(

Offline pjk

  • Multiple posting newcomer
  • *
  • Posts: 13
Re: A note about the Windows builds
« Reply #25 on: December 27, 2005, 01:03:22 am »
Can I bring this thread back to the build process
 Quote from tiwag December 22, 2005, 12:48:42 PM
Quote
The inconsistent usage of WX_CFG in these project files (sometimes set to "NonUnicode", sometimes set to "" ) is
really annoying and last not least a reason, why some ( less experienced ) users couldn't build a SVN version by themself.
As a less experience user who has been compiling the svn version I would like to suggest that as changes are made to the build process the build instructions in svn trunck should be kept reasonably up to date and a little more detailed. I don't think it needs quite the detail of thomas'  Compiling CodeBlocks for Windows ( ANSI and Unicode) from December 19, 2005, 10:47:44 AM - http://forums.codeblocks.org/index.php?topic=1701.0 , but the basic instructions.
It may be that you do not want to encourage less experience user to try the svn version, but I would have thought more testers would be better. From my point of view the features that interest me most are constantly improving and I want to be up to date with this.
The cause of most of my confusion was instructions about compiling wxwidgets with VENDOR=cb option and then moving to a seperate folder, which appears in many places in the wiki and the forum.
There does seem to be some sense in maintaining a specific codeblocks wxwidgets dll because you may not always want to compile codeblocks with the latest wxwidgets but may want it for other projects. Perhaps the best answer is to use a seperate tree forthe codeblocks version of wxwidgets (lib and include).

Offline grv575

  • Official tester
  • Regular
  • ***
  • Posts: 381
Re: A note about the Windows builds
« Reply #26 on: December 27, 2005, 11:18:39 pm »
Yeah that page has to be cleaned up.  It's a patchwork of many different ways of building over time.  The part about moving or renaming directories is not needed, as this can be done by passing CFG=Unicode or CFG=NonUnicode.  In addition, the CFG flag should probably be ommitted, unless you do want seperate codeblocks and other wxwidgets dlls -- just having Unicode and ANSI wxwidgets dlls in the same directory is supported and works fine.  Btw, it is a wiki, so anyone can make changes to it -- the reason it isn't always up to date like larger project (uhhh kde or something) is time commitment (although code improvements are rapidly added to the SVN repository in preparation for a 1.0 release).