[m-rev.] for review: unicode command line arguments on windows

[Peter Wang]

On Thu, 15 Dec 2011 16:07:34 +1100 (EST), Julien Fischer <juliensf at csse.unimelb.edu.au> wrote:
> >
> > Can you test this on MSVC?
> 
> Ok, for any executable that is not the compiler, e.g mslice.exe,
> mercury_profile.exe, we get the following error:
> 
> error LNK2019: unresolved external symbol __wgetmainargs referenced in
> function _mercury_win32_args
> 
> Is __wgetmainargs included in the static version of the library on
> Windows, i.e. in libcmt.lib?  Or is only part of the dynamic library?
> (MSDN is its unsual unhelpful self on this issue.)

I guess?
http://code.google.com/p/msysgit/source/detail?r=43adf7bb24&repo=4msysgit

For MSVC we have the option of using
    wmain(int argc, wchar_t *argv[], wchar_t *envp[])

> I will try reconfuring with --with-msvcrt enabled and see if that helps.
> In the meantime, This is all rather curious, because mercury_compile.exe
> does build (and indeed runs).  Any idea what we might be doing
> differently in the compiler directory?

The compiler uses main.c and not the output of mkinit.

Peter
--------------------------------------------------------------------------
mercury-reviews mailing list
Post messages to:       mercury-reviews at csse.unimelb.edu.au
Administrative Queries: owner-mercury-reviews at csse.unimelb.edu.au
Subscriptions:          mercury-reviews-request at csse.unimelb.edu.au
--------------------------------------------------------------------------