[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
I was in windows today and downloaded the free MSVC command line tools
to try and compile allegro with it (to eventually track down that race
condition bug AJ was having). The first problem I hit was, it installed
into a patch with spaces. The attached patch was a quick hack to fix
this (it may break other things though).
the spaces issue has been around for quite a while.
the way to fix it is to use the short ~1 form.
And I'm wondering, were we always forcing regular MSVC users to install
into a path with no spaces? There seems to be no more way in winXP to
find out that DOS-path without spaces name of a dir, as mentioned in the
error message - so hopefully this patch fixes that as well.
(And about compiling allegro with the free cl.exe.. after fixing the
spaces issue, it compiled some files until I discovered that it doesn't
come with windows.h, and it chokes on the windows.h in mingw, so no
success.)
i find that a little odd, if it does not come with the most important
(often used) header file, its not much of a compiler.
maybe you need to install an SDK to get it. ?!?
i will look into that tonight.
i also think you should not waste time chasing this bug until you have some
more evidence.
part of the reason i think no one has tackled it yet is because its not
easy to find / fix.
lets gather a lot more evidence 1st to make the bug chasing a bit easier.
bob hinted at it being around for quite a while, maybe he can elaborate on
what he thinks it might be.
Elias Pschernig
-----------------------
Andrew. J. Baxter
ph: 0421-785-186
email: aj@xxxxxxxxxx