public inbox for libffi-discuss@sourceware.org
 help / color / mirror / Atom feed
* How to compile on Windows?
@ 2012-01-04 22:10 Nathan Rajlich
  2012-01-04 22:59 ` Timothy Wall
  0 siblings, 1 reply; 9+ messages in thread
From: Nathan Rajlich @ 2012-01-04 22:10 UTC (permalink / raw)
  To: libffi-discuss

Hello all,

I am attempting to compile libffi on windows, and am having some
trouble. I was able to figure out how to get the "configure" step to
work by using the provided example in the README. The configure step
completed successfully and the necessary .h and Makefiles were
created.

Now when I try to invoke 'nmake', it quits quickly with an error
saying "Illegal '\' character in macro. Quitting." or something along
those lines, and I'm not sure where to take it from here.

Any advice would be much appreciated! Thanks in advance!

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: How to compile on Windows?
  2012-01-04 22:10 How to compile on Windows? Nathan Rajlich
@ 2012-01-04 22:59 ` Timothy Wall
  2012-01-04 23:03   ` Nathan Rajlich
  0 siblings, 1 reply; 9+ messages in thread
From: Timothy Wall @ 2012-01-04 22:59 UTC (permalink / raw)
  To: Nathan Rajlich; +Cc: libffi-discuss

Are you trying to compile with MSVC or gcc/mingw?

Regardless of compiler, I doubt you'll be able to get "nmake" to work on configure-generated makefiles; you'll need either cygwin or MSYS-based make.

On Jan 4, 2012, at 5:09 PM, Nathan Rajlich wrote:

> Hello all,
> 
> I am attempting to compile libffi on windows, and am having some
> trouble. I was able to figure out how to get the "configure" step to
> work by using the provided example in the README. The configure step
> completed successfully and the necessary .h and Makefiles were
> created.
> 
> Now when I try to invoke 'nmake', it quits quickly with an error
> saying "Illegal '\' character in macro. Quitting." or something along
> those lines, and I'm not sure where to take it from here.
> 
> Any advice would be much appreciated! Thanks in advance!

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: How to compile on Windows?
  2012-01-04 22:59 ` Timothy Wall
@ 2012-01-04 23:03   ` Nathan Rajlich
  2012-01-04 23:08     ` Timothy Wall
  0 siblings, 1 reply; 9+ messages in thread
From: Nathan Rajlich @ 2012-01-04 23:03 UTC (permalink / raw)
  To: libffi-discuss

Thanks for the quick replies guys.

I am trying to use the MSVC compiler. I do have the Git Bash installed
though, which is how I was able to execute the configure script.
Executing 'dmake' after getting a download of it displays:

dmake.exe: Error -- /bin/sh: No such file or directory

Any ideas?

On Wed, Jan 4, 2012 at 2:58 PM, Timothy Wall <twall@users.sf.net> wrote:
> Are you trying to compile with MSVC or gcc/mingw?
>
> Regardless of compiler, I doubt you'll be able to get "nmake" to work on configure-generated makefiles; you'll need either cygwin or MSYS-based make.
>
> On Jan 4, 2012, at 5:09 PM, Nathan Rajlich wrote:
>
>> Hello all,
>>
>> I am attempting to compile libffi on windows, and am having some
>> trouble. I was able to figure out how to get the "configure" step to
>> work by using the provided example in the README. The configure step
>> completed successfully and the necessary .h and Makefiles were
>> created.
>>
>> Now when I try to invoke 'nmake', it quits quickly with an error
>> saying "Illegal '\' character in macro. Quitting." or something along
>> those lines, and I'm not sure where to take it from here.
>>
>> Any advice would be much appreciated! Thanks in advance!
>

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: How to compile on Windows?
  2012-01-04 23:03   ` Nathan Rajlich
@ 2012-01-04 23:08     ` Timothy Wall
  2012-01-04 23:13       ` Nathan Rajlich
  0 siblings, 1 reply; 9+ messages in thread
From: Timothy Wall @ 2012-01-04 23:08 UTC (permalink / raw)
  To: Nathan Rajlich; +Cc: libffi-discuss

"configure" relies on more than just the shell; you need either msys (from mingw) or cygwin.

You should get configure/compile working with gcc/mingw before you try it with msvc, since while libffi includes some wrapper scripts to work with MSVC, I'm not certain they will work out of the box, so you want to make sure everything else is resolved first.



On Jan 4, 2012, at 6:03 PM, Nathan Rajlich wrote:

> Thanks for the quick replies guys.
> 
> I am trying to use the MSVC compiler. I do have the Git Bash installed
> though, which is how I was able to execute the configure script.
> Executing 'dmake' after getting a download of it displays:
> 
> dmake.exe: Error -- /bin/sh: No such file or directory
> 
> Any ideas?
> 
> On Wed, Jan 4, 2012 at 2:58 PM, Timothy Wall <twall@users.sf.net> wrote:
>> Are you trying to compile with MSVC or gcc/mingw?
>> 
>> Regardless of compiler, I doubt you'll be able to get "nmake" to work on configure-generated makefiles; you'll need either cygwin or MSYS-based make.
>> 
>> On Jan 4, 2012, at 5:09 PM, Nathan Rajlich wrote:
>> 
>>> Hello all,
>>> 
>>> I am attempting to compile libffi on windows, and am having some
>>> trouble. I was able to figure out how to get the "configure" step to
>>> work by using the provided example in the README. The configure step
>>> completed successfully and the necessary .h and Makefiles were
>>> created.
>>> 
>>> Now when I try to invoke 'nmake', it quits quickly with an error
>>> saying "Illegal '\' character in macro. Quitting." or something along
>>> those lines, and I'm not sure where to take it from here.
>>> 
>>> Any advice would be much appreciated! Thanks in advance!
>> 

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: How to compile on Windows?
  2012-01-04 23:08     ` Timothy Wall
@ 2012-01-04 23:13       ` Nathan Rajlich
  2012-01-04 23:23         ` Timothy Wall
  0 siblings, 1 reply; 9+ messages in thread
From: Nathan Rajlich @ 2012-01-04 23:13 UTC (permalink / raw)
  To: libffi-discuss

Hhmm, ok I guess I can try messing around with gcc/mingw first. I was
just under the impression that building with MSVC would work from the
example in the README:

path/to/configure CC=path/to/msvcc.sh LD=link CPP=\"cl -nologo -EP\"

Unfortunately it doesn't say what to do past that point :p

On Wed, Jan 4, 2012 at 3:07 PM, Timothy Wall <twall@users.sf.net> wrote:
> "configure" relies on more than just the shell; you need either msys (from mingw) or cygwin.
>
> You should get configure/compile working with gcc/mingw before you try it with msvc, since while libffi includes some wrapper scripts to work with MSVC, I'm not certain they will work out of the box, so you want to make sure everything else is resolved first.
>
>
>
> On Jan 4, 2012, at 6:03 PM, Nathan Rajlich wrote:
>
>> Thanks for the quick replies guys.
>>
>> I am trying to use the MSVC compiler. I do have the Git Bash installed
>> though, which is how I was able to execute the configure script.
>> Executing 'dmake' after getting a download of it displays:
>>
>> dmake.exe: Error -- /bin/sh: No such file or directory
>>
>> Any ideas?
>>
>> On Wed, Jan 4, 2012 at 2:58 PM, Timothy Wall <twall@users.sf.net> wrote:
>>> Are you trying to compile with MSVC or gcc/mingw?
>>>
>>> Regardless of compiler, I doubt you'll be able to get "nmake" to work on configure-generated makefiles; you'll need either cygwin or MSYS-based make.
>>>
>>> On Jan 4, 2012, at 5:09 PM, Nathan Rajlich wrote:
>>>
>>>> Hello all,
>>>>
>>>> I am attempting to compile libffi on windows, and am having some
>>>> trouble. I was able to figure out how to get the "configure" step to
>>>> work by using the provided example in the README. The configure step
>>>> completed successfully and the necessary .h and Makefiles were
>>>> created.
>>>>
>>>> Now when I try to invoke 'nmake', it quits quickly with an error
>>>> saying "Illegal '\' character in macro. Quitting." or something along
>>>> those lines, and I'm not sure where to take it from here.
>>>>
>>>> Any advice would be much appreciated! Thanks in advance!
>>>
>

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: How to compile on Windows?
  2012-01-04 23:13       ` Nathan Rajlich
@ 2012-01-04 23:23         ` Timothy Wall
  2012-01-04 23:35           ` Nathan Rajlich
  0 siblings, 1 reply; 9+ messages in thread
From: Timothy Wall @ 2012-01-04 23:23 UTC (permalink / raw)
  To: Nathan Rajlich; +Cc: libffi-discuss

If your configure worked fine with that line, then it's quite possible that your "make" will work given a proper "make" program.

Last I tried that configuration it didn't work for me, though I might have gotten something else wrong.  

On Jan 4, 2012, at 6:12 PM, Nathan Rajlich wrote:

> Hhmm, ok I guess I can try messing around with gcc/mingw first. I was
> just under the impression that building with MSVC would work from the
> example in the README:
> 
> path/to/configure CC=path/to/msvcc.sh LD=link CPP=\"cl -nologo -EP\"
> 
> Unfortunately it doesn't say what to do past that point :p
> 
> On Wed, Jan 4, 2012 at 3:07 PM, Timothy Wall <twall@users.sf.net> wrote:
>> "configure" relies on more than just the shell; you need either msys (from mingw) or cygwin.
>> 
>> You should get configure/compile working with gcc/mingw before you try it with msvc, since while libffi includes some wrapper scripts to work with MSVC, I'm not certain they will work out of the box, so you want to make sure everything else is resolved first.
>> 
>> 
>> 
>> On Jan 4, 2012, at 6:03 PM, Nathan Rajlich wrote:
>> 
>>> Thanks for the quick replies guys.
>>> 
>>> I am trying to use the MSVC compiler. I do have the Git Bash installed
>>> though, which is how I was able to execute the configure script.
>>> Executing 'dmake' after getting a download of it displays:
>>> 
>>> dmake.exe: Error -- /bin/sh: No such file or directory
>>> 
>>> Any ideas?
>>> 
>>> On Wed, Jan 4, 2012 at 2:58 PM, Timothy Wall <twall@users.sf.net> wrote:
>>>> Are you trying to compile with MSVC or gcc/mingw?
>>>> 
>>>> Regardless of compiler, I doubt you'll be able to get "nmake" to work on configure-generated makefiles; you'll need either cygwin or MSYS-based make.
>>>> 
>>>> On Jan 4, 2012, at 5:09 PM, Nathan Rajlich wrote:
>>>> 
>>>>> Hello all,
>>>>> 
>>>>> I am attempting to compile libffi on windows, and am having some
>>>>> trouble. I was able to figure out how to get the "configure" step to
>>>>> work by using the provided example in the README. The configure step
>>>>> completed successfully and the necessary .h and Makefiles were
>>>>> created.
>>>>> 
>>>>> Now when I try to invoke 'nmake', it quits quickly with an error
>>>>> saying "Illegal '\' character in macro. Quitting." or something along
>>>>> those lines, and I'm not sure where to take it from here.
>>>>> 
>>>>> Any advice would be much appreciated! Thanks in advance!
>>>> 
>> 

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: How to compile on Windows?
  2012-01-04 23:23         ` Timothy Wall
@ 2012-01-04 23:35           ` Nathan Rajlich
  2012-01-05 17:25             ` Nathan Rajlich
  0 siblings, 1 reply; 9+ messages in thread
From: Nathan Rajlich @ 2012-01-04 23:35 UTC (permalink / raw)
  To: libffi-discuss

Well here's the full output of running the "configure" command on my
Windows box: https://gist.github.com/1562838

However, here's the output of executing the make.exe from the gnuwin32
ports site: https://gist.github.com/1562844

So still stuck here. Thanks for the help so far again though!

On Wed, Jan 4, 2012 at 3:22 PM, Timothy Wall <twall@users.sf.net> wrote:
> If your configure worked fine with that line, then it's quite possible that your "make" will work given a proper "make" program.
>
> Last I tried that configuration it didn't work for me, though I might have gotten something else wrong.
>
> On Jan 4, 2012, at 6:12 PM, Nathan Rajlich wrote:
>
>> Hhmm, ok I guess I can try messing around with gcc/mingw first. I was
>> just under the impression that building with MSVC would work from the
>> example in the README:
>>
>> path/to/configure CC=path/to/msvcc.sh LD=link CPP=\"cl -nologo -EP\"
>>
>> Unfortunately it doesn't say what to do past that point :p
>>
>> On Wed, Jan 4, 2012 at 3:07 PM, Timothy Wall <twall@users.sf.net> wrote:
>>> "configure" relies on more than just the shell; you need either msys (from mingw) or cygwin.
>>>
>>> You should get configure/compile working with gcc/mingw before you try it with msvc, since while libffi includes some wrapper scripts to work with MSVC, I'm not certain they will work out of the box, so you want to make sure everything else is resolved first.
>>>
>>>
>>>
>>> On Jan 4, 2012, at 6:03 PM, Nathan Rajlich wrote:
>>>
>>>> Thanks for the quick replies guys.
>>>>
>>>> I am trying to use the MSVC compiler. I do have the Git Bash installed
>>>> though, which is how I was able to execute the configure script.
>>>> Executing 'dmake' after getting a download of it displays:
>>>>
>>>> dmake.exe: Error -- /bin/sh: No such file or directory
>>>>
>>>> Any ideas?
>>>>
>>>> On Wed, Jan 4, 2012 at 2:58 PM, Timothy Wall <twall@users.sf.net> wrote:
>>>>> Are you trying to compile with MSVC or gcc/mingw?
>>>>>
>>>>> Regardless of compiler, I doubt you'll be able to get "nmake" to work on configure-generated makefiles; you'll need either cygwin or MSYS-based make.
>>>>>
>>>>> On Jan 4, 2012, at 5:09 PM, Nathan Rajlich wrote:
>>>>>
>>>>>> Hello all,
>>>>>>
>>>>>> I am attempting to compile libffi on windows, and am having some
>>>>>> trouble. I was able to figure out how to get the "configure" step to
>>>>>> work by using the provided example in the README. The configure step
>>>>>> completed successfully and the necessary .h and Makefiles were
>>>>>> created.
>>>>>>
>>>>>> Now when I try to invoke 'nmake', it quits quickly with an error
>>>>>> saying "Illegal '\' character in macro. Quitting." or something along
>>>>>> those lines, and I'm not sure where to take it from here.
>>>>>>
>>>>>> Any advice would be much appreciated! Thanks in advance!
>>>>>
>>>
>

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: How to compile on Windows?
  2012-01-04 23:35           ` Nathan Rajlich
@ 2012-01-05 17:25             ` Nathan Rajlich
  2012-01-05 17:29               ` Cauê Waneck
  0 siblings, 1 reply; 9+ messages in thread
From: Nathan Rajlich @ 2012-01-05 17:25 UTC (permalink / raw)
  To: libffi-discuss

So I was able to figure out how to get it built properly using
MozillaBuild[0]'s make command, along with the configure command I had
already run successfully. Thanks again!

0: http://ftp.mozilla.org/pub/mozilla.org/mozilla/libraries/win32/MozillaBuildSetup-Latest.exe

On Wed, Jan 4, 2012 at 3:34 PM, Nathan Rajlich <nathan@tootallnate.net> wrote:
> Well here's the full output of running the "configure" command on my
> Windows box: https://gist.github.com/1562838
>
> However, here's the output of executing the make.exe from the gnuwin32
> ports site: https://gist.github.com/1562844
>
> So still stuck here. Thanks for the help so far again though!
>
> On Wed, Jan 4, 2012 at 3:22 PM, Timothy Wall <twall@users.sf.net> wrote:
>> If your configure worked fine with that line, then it's quite possible that your "make" will work given a proper "make" program.
>>
>> Last I tried that configuration it didn't work for me, though I might have gotten something else wrong.
>>
>> On Jan 4, 2012, at 6:12 PM, Nathan Rajlich wrote:
>>
>>> Hhmm, ok I guess I can try messing around with gcc/mingw first. I was
>>> just under the impression that building with MSVC would work from the
>>> example in the README:
>>>
>>> path/to/configure CC=path/to/msvcc.sh LD=link CPP=\"cl -nologo -EP\"
>>>
>>> Unfortunately it doesn't say what to do past that point :p
>>>
>>> On Wed, Jan 4, 2012 at 3:07 PM, Timothy Wall <twall@users.sf.net> wrote:
>>>> "configure" relies on more than just the shell; you need either msys (from mingw) or cygwin.
>>>>
>>>> You should get configure/compile working with gcc/mingw before you try it with msvc, since while libffi includes some wrapper scripts to work with MSVC, I'm not certain they will work out of the box, so you want to make sure everything else is resolved first.
>>>>
>>>>
>>>>
>>>> On Jan 4, 2012, at 6:03 PM, Nathan Rajlich wrote:
>>>>
>>>>> Thanks for the quick replies guys.
>>>>>
>>>>> I am trying to use the MSVC compiler. I do have the Git Bash installed
>>>>> though, which is how I was able to execute the configure script.
>>>>> Executing 'dmake' after getting a download of it displays:
>>>>>
>>>>> dmake.exe: Error -- /bin/sh: No such file or directory
>>>>>
>>>>> Any ideas?
>>>>>
>>>>> On Wed, Jan 4, 2012 at 2:58 PM, Timothy Wall <twall@users.sf.net> wrote:
>>>>>> Are you trying to compile with MSVC or gcc/mingw?
>>>>>>
>>>>>> Regardless of compiler, I doubt you'll be able to get "nmake" to work on configure-generated makefiles; you'll need either cygwin or MSYS-based make.
>>>>>>
>>>>>> On Jan 4, 2012, at 5:09 PM, Nathan Rajlich wrote:
>>>>>>
>>>>>>> Hello all,
>>>>>>>
>>>>>>> I am attempting to compile libffi on windows, and am having some
>>>>>>> trouble. I was able to figure out how to get the "configure" step to
>>>>>>> work by using the provided example in the README. The configure step
>>>>>>> completed successfully and the necessary .h and Makefiles were
>>>>>>> created.
>>>>>>>
>>>>>>> Now when I try to invoke 'nmake', it quits quickly with an error
>>>>>>> saying "Illegal '\' character in macro. Quitting." or something along
>>>>>>> those lines, and I'm not sure where to take it from here.
>>>>>>>
>>>>>>> Any advice would be much appreciated! Thanks in advance!
>>>>>>
>>>>
>>

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: How to compile on Windows?
  2012-01-05 17:25             ` Nathan Rajlich
@ 2012-01-05 17:29               ` Cauê Waneck
  0 siblings, 0 replies; 9+ messages in thread
From: Cauê Waneck @ 2012-01-05 17:29 UTC (permalink / raw)
  To: Nathan Rajlich; +Cc: libffi-discuss

Hi,

It was hard to compile to windows via MSVC, but I made this batch
helper that takes care of compiling the .S file. The rest I'm using a
custom haxe build pipeline, but you can just compile the rest of the
needed c files and link them all together (along with win32.obj
created by this batch file)

http://code.google.com/p/hxffi/source/browse/trunk/haxelib/project/buildwin32.bat

Hope it helps! :)
Cauê

2012/1/5 Nathan Rajlich <nathan@tootallnate.net>:
> So I was able to figure out how to get it built properly using
> MozillaBuild[0]'s make command, along with the configure command I had
> already run successfully. Thanks again!
>
> 0: http://ftp.mozilla.org/pub/mozilla.org/mozilla/libraries/win32/MozillaBuildSetup-Latest.exe
>
> On Wed, Jan 4, 2012 at 3:34 PM, Nathan Rajlich <nathan@tootallnate.net> wrote:
>> Well here's the full output of running the "configure" command on my
>> Windows box: https://gist.github.com/1562838
>>
>> However, here's the output of executing the make.exe from the gnuwin32
>> ports site: https://gist.github.com/1562844
>>
>> So still stuck here. Thanks for the help so far again though!
>>
>> On Wed, Jan 4, 2012 at 3:22 PM, Timothy Wall <twall@users.sf.net> wrote:
>>> If your configure worked fine with that line, then it's quite possible that your "make" will work given a proper "make" program.
>>>
>>> Last I tried that configuration it didn't work for me, though I might have gotten something else wrong.
>>>
>>> On Jan 4, 2012, at 6:12 PM, Nathan Rajlich wrote:
>>>
>>>> Hhmm, ok I guess I can try messing around with gcc/mingw first. I was
>>>> just under the impression that building with MSVC would work from the
>>>> example in the README:
>>>>
>>>> path/to/configure CC=path/to/msvcc.sh LD=link CPP=\"cl -nologo -EP\"
>>>>
>>>> Unfortunately it doesn't say what to do past that point :p
>>>>
>>>> On Wed, Jan 4, 2012 at 3:07 PM, Timothy Wall <twall@users.sf.net> wrote:
>>>>> "configure" relies on more than just the shell; you need either msys (from mingw) or cygwin.
>>>>>
>>>>> You should get configure/compile working with gcc/mingw before you try it with msvc, since while libffi includes some wrapper scripts to work with MSVC, I'm not certain they will work out of the box, so you want to make sure everything else is resolved first.
>>>>>
>>>>>
>>>>>
>>>>> On Jan 4, 2012, at 6:03 PM, Nathan Rajlich wrote:
>>>>>
>>>>>> Thanks for the quick replies guys.
>>>>>>
>>>>>> I am trying to use the MSVC compiler. I do have the Git Bash installed
>>>>>> though, which is how I was able to execute the configure script.
>>>>>> Executing 'dmake' after getting a download of it displays:
>>>>>>
>>>>>> dmake.exe: Error -- /bin/sh: No such file or directory
>>>>>>
>>>>>> Any ideas?
>>>>>>
>>>>>> On Wed, Jan 4, 2012 at 2:58 PM, Timothy Wall <twall@users.sf.net> wrote:
>>>>>>> Are you trying to compile with MSVC or gcc/mingw?
>>>>>>>
>>>>>>> Regardless of compiler, I doubt you'll be able to get "nmake" to work on configure-generated makefiles; you'll need either cygwin or MSYS-based make.
>>>>>>>
>>>>>>> On Jan 4, 2012, at 5:09 PM, Nathan Rajlich wrote:
>>>>>>>
>>>>>>>> Hello all,
>>>>>>>>
>>>>>>>> I am attempting to compile libffi on windows, and am having some
>>>>>>>> trouble. I was able to figure out how to get the "configure" step to
>>>>>>>> work by using the provided example in the README. The configure step
>>>>>>>> completed successfully and the necessary .h and Makefiles were
>>>>>>>> created.
>>>>>>>>
>>>>>>>> Now when I try to invoke 'nmake', it quits quickly with an error
>>>>>>>> saying "Illegal '\' character in macro. Quitting." or something along
>>>>>>>> those lines, and I'm not sure where to take it from here.
>>>>>>>>
>>>>>>>> Any advice would be much appreciated! Thanks in advance!
>>>>>>>
>>>>>
>>>

^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2012-01-05 17:29 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-01-04 22:10 How to compile on Windows? Nathan Rajlich
2012-01-04 22:59 ` Timothy Wall
2012-01-04 23:03   ` Nathan Rajlich
2012-01-04 23:08     ` Timothy Wall
2012-01-04 23:13       ` Nathan Rajlich
2012-01-04 23:23         ` Timothy Wall
2012-01-04 23:35           ` Nathan Rajlich
2012-01-05 17:25             ` Nathan Rajlich
2012-01-05 17:29               ` Cauê Waneck

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).