[texworks] Building on Windows 7

Casey P. Johnson cpj at math.utah.edu
Tue Feb 23 15:29:08 CET 2010

Thanks. That did it. I did have the plugins in the
texworks-read-only/plugins directory, but I mistyped it in my original

Incidentally, on my 64-bit machine I was receiving the following error:

c:/bin/Python26/libs/python26.lib(python26.dll): Recognised but unhandled
machine type (0x8664) in Import Library Format archive

Followed by a slew of messages similar to :
obj/TWPythonPlugin.o:TWPythonPlugin.cpp:(.text+0xa8): undefined reference
to `_imp___PyObject_New'

I switched from ActivePython x64 2.6.4 to the installation provided at
python.org (also 2.6.4) and it worked immediately. I have no idea what
made the difference, but I thought I would put it out there in case anyone
else comes across the same problem.


> Hi,
> Am 2010-02-23 00:13, schrieb Casey P. Johnson:
>> I'm sorry to be a bother, but I am having trouble building the latest
>> revision. It seems to be related to the plugin functionality. I have
>> compiled the two plugins and placed the .dll files in texworks-read-only
>> as instructed in the faq, but I get the following errors:
>> ./obj\TWScriptable.o:TWScriptable.cpp:(.text+0xa): undefined reference
>> to
>> `qt_pl
>> ugin_instance_TWLuaPlugin()'
>> ./obj\TWScriptable.o:TWScriptable.cpp:(.text+0x19): undefined reference
>> to
>> `qt_p
>> lugin_instance_TWPythonPlugin()'
> I believe this can easily be fixed by commenting out the line
> "QMAKE_CXXFLAGS += -DSTATIC_SCRIPTING_PLUGINS" (by prefixing it with a
> '#').
> BTW: The dlls should go into texworks-read-only/plugins.
> Stefan

More information about the texworks mailing list