Just a testmail. please ignore
--
Sincerely Yours
Sascha Manns
openSUSE Community & Support Agent
openSUSE Membership Comitee
openSUSE Electioncomitee
openSUSE Marketing Team
Packager in Build Service
Blog: http://saigkill.wordpress.com
Web: http://www.saschamanns.de
--
To unsubscribe, e-mail: opensuse-programming+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-programming+help(a)opensuse.org
I am using the MinGW cross compiler from in windows:mingw in OBS to make
on Linux binaries that run on Windows. It really works great. But would
I only share that bit of good news? Naah. I have a small issue and am
curious if I am alone: the binaries that are produced are not expanding
command line wild cards.
A bit of background: on windows, the good old command.com (or cmd.exe)
does not expand file name wild cards. They are passed to the application
unchanged. Microsoft VC++, for example, lets you link with a runtime
startup module that performs this expansion before main() is called. As
I understand it, the MinGW compiler should be doing the same. In fact,
if I understand correctly, it should be the default behavior.
Alas, it is not happening. Is anyone else using this cross compiler? Is
anyone else getting it to expand wild cards properly?
Yours sincerely,
Roger Oberholtzer
OPQ Systems / Ramböll RST
Office: Int +46 10-615 60 20
Mobile: Int +46 70-815 1696
roger.oberholtzer(a)ramboll.se
________________________________________
Ramböll Sverige AB
Krukmakargatan 21
P.O. Box 17009
SE-104 62 Stockholm, Sweden
www.rambollrst.se
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org
--
To unsubscribe, e-mail: opensuse-programming+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-programming+help(a)opensuse.org