From: Slava P. <sl...@fa...> - 2011-09-20 22:37:59
|
Hi John, On Tue, Sep 20, 2011 at 2:45 PM, John Porubek <jpo...@gm...> wrote: > Thanks for the response. So I was barking up the wrong tree, huh? > Nothing new there. Good thing I asked the question. Isn't there some > way I can use Factor's built-in debugging support to at least tell me > which specific image is not being found so I could have more of a clue > as to what's going wrong? There's code in the git repository for this. We should have a Windows binary soon. > I also tried to get it working in Windows 7 after I downloaded and > installed "oalinst" and "freealut-1.1,0-bin". The installer put the > "OpenAL32.dll" file in C:\Windows\System32, so I put "alut.dll" there, > too. However, the examples that came with "freealut" wouldn't work > until I put "alut.dll" in C:\Windows, so I put a copy of > "OpenAL32.dll" there, too. No joy. I still get the same "The image > refers to a library or symbol that was not found at load time" > message. Is your copy of Factor a 64-bit build? If so, the libraries have to be 64-bit (or vice versa). > But I'm mostly happy to have it working under Linux. I prefer Linux > for most of my development work and I've come to accept that Windows > is sort of the "poor step child" in the world of Factor. Examples of > this are the lack of real serial port support for Windows and the fact > that none of the demo slide shows display properly under Windows. Other than that, most things do work on Windows. I forgot about the slide show thing; I'll file a bug about it. Cheers, Slava |