Francesco Montorsi wrote:
Anyway, i think batch build is the only feasible way to work with the
bakefile generated project files on VC.
I've never completely understood this: why do you need to build more
than one configuration with MSVC projects ?
For testing or for development or both ?
I would prefer to build only one configuration like in Cmake their is
the ALLBuild target, which buils all othere target for the active
configuration set to the ALLBuild target.
The problem is that if you use wx project files, their is no such
overall target.
So all seperate targets have to be set by hand to a certain active
target, this is bad if there are many.
So one goes to batch build, and selects the configurations of all
targets which need to be build.
No that is doable, although also not ideal, since there are many
flavours for each target, you best deselect all flavours for all targets
first, and next select the release and debug multilib targets, and build
those for all targets.
(The trick to deselect all, is selecting the first and Shift select the
last and press the space bar)
To test if a project compiles and works in all configs I think it's
best to use command line makefiles where you can script all builds;
for development I usually use IDE too but I always select 1 config and
I've never used batch builds.
As i explained above, if there are many targets, how do you set all
seperate targets right.
Testing using makefiles is oke, but of course the project files need to
work too.
Also i see no reason why i need to type (n)make first on the command
line and next open a project file to start developing where this is also
part of the project file.
I only use project files when i can ;-)
yes, you're right.
But currently it would require do a lot of changes in all components
bakefiles which would then turn useless as soon as future versions of
bakefile are out. So I prefer to make the Big Step in wxCode only when
I'm sure that they will be permanent changes ;)
I think we better mention this in the install.html, because it is
confusing.
So we must tell that wxstedit needs to be compiled in only one flavour(
debug or release and what about the rest? ).
And that only this flavours sshould be used in wxLua too. The other make
no sence, even when using makefile right?
Because using a debug wxstedit in a release wxLua is also wrong.
Do you have any idea how we can speed up the patches for bakefile?
maybe reporting that the patch worked for you could help... e.g.:
http://sourceforge.net/tracker/index.php?func=detail&aid=1376223&group_id=83016&atid=568031
Did it :-))
Is there only a time problem, or are there other issues?
basically, it's a time problem of Vaclav. He said he won't give me CVS
(or better SVN now) access because my patches often needs fixes before
being applied. And that's true :(
Sometimes is very difficult to foresee all situations where some code
could be used...
That i can understand. But not having time was for me the excuse to give
many people access to wxArt2D.
No progress is worse then solving a problem here and there when it pops up.
Go with the flow is my moto, and it pays off, does it not ;-)
Klaas
--
Unclassified
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Wxlua-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wxlua-users
