On Tuesday, 12 August 2014 at 22:25:24 UTC, Johnathan Sunders
wrote:
I'm having an issue with building programs that link with LuaD
using VisualD. If I use Dub, it builds without an issue, but
generating a project file and compiling it through VisualD
results in Error 162: Bad Type Index reference to type 84A9
when linking luad.lib(base).
Anyone has any ideas on what may cause this? I've also tried
building using the VisualD project on LuaD's GitHub in case it
was a missing configuration setting but that has the same issue
(running Windows 8 64 bit in case it's relevant).
I wondered if you ever found a solution to this issue? I am
having exactly the same problem. Basically I did this
1. Generated a simple app with dub and added luad as a dependency.
2. Compiling the app with dub works fine. Can call Lua ok.
3. Asking dub to generate a VisualD project file and then trying
to compile the same app in VisualD fails, in my case the error is
Error 162: Bad Type Index reference to type 5C55.
I have tried copying the VisualD project from the dub's Luad
folder into my own solution and compiling it manually, but I run
into the same problem.
As an aside, I should add that this is an attempt to workaround
my original problem - I want to use a dub package (LuaD) in an
existing VisualD project that I created using VisualD - not sure
if that is possible?
Wild guess: There is an enigmatic README.md in the LuaD
distribution
https://github.com/JakobOvrum/LuaD/blob/master/extlib/README.md
which might contain a clue as to the problem.
I am running Windows 8 64 bit, the VisualD project is Win32
configuration. Changing the configuration to Win64 yields error
..\luad-master\extlib\lua5.1.lib : fatal error LNK1136: invalid
or corrupt file
