Compiling on windows

User avatar
tsuujin
Posts: 695
Joined: Fri Feb 26, 2010 12:59 am
Location: California
Contact:

Compiling on windows

Post by tsuujin »

Hi there, trying to compile the latest build on windows for the first time (odd to do such a thing on windows, I'm so used to linux) and I've hit a snag.

I'm using this guide to compile, and everything works great right up to the point where I actually attempt to compile the beta sources. At which point I get this:
C:\Mudlet\beta\src>cmake -G "MinGW Makefiles"
-- Found QScintilla2: C:/Mudlet/Qt/4.4.3/lib/libqscintilla2.a
CMake Error at C:/Mudlet/CMake 2.6/share/cmake-2.6/Modules/FindPackageHandleStan
dardArgs.cmake:57 (MESSAGE):
Could NOT find PCRE (missing: PCRE_LIBRARIES)
Call Stack (most recent call first):
C:/Mudlet/beta/cmake/FindPCRE.cmake:76 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
CMakeLists.txt:123 (FIND_PACKAGE)


-- Configuring incomplete, errors occurred!
Now, I've done a few things to try to remedy this. First: I've downloaded both the linked version of PCRE (7.8) and the latest (8.12), compiled them both with no errors and attempted to insert them into the PATH before compiling Mudlet. I've also gone forward and done the "make install" and then inserted the install path into the PATH and tried again with both versions. No go.

I can't think of any legitimate reason that cmake wouldn't be able to find the PCRE libraries, so I'm stuck. Any suggestions?

For Reference, here's my current output of the 7.8 cmake:
C:\Mudlet\pcre-7.8>cmake -DBUILD_SHARED_LIBS:BOOL=ON -G "MinGW Makefiles"
-- Could not find OPTIONAL package BZip2
-- Could not find OPTIONAL package Readline
--
--
-- PCRE configuration summary:
--
-- Install prefix .................. : C:/Program Files (x86)/PCRE
-- C compiler ...................... : C:/Mudlet/MinGW/bin/gcc.exe
-- C++ compiler .................... : C:/Mudlet/MinGW/bin/g++.exe
-- C compiler flags ................ :
-- C++ compiler flags .............. :
--
-- Build C++ library ............... : ON
-- Enable UTF-8 support ............ : OFF
-- Unicode properties .............. : OFF
-- Newline char/sequence ........... : LF
-- \R matches only ANYCRLF ......... : OFF
-- EBCDIC coding ................... : OFF
-- Rebuild char tables ............. : OFF
-- No stack recursion .............. : OFF
-- POSIX mem threshold ............. : 10
-- Internal link size .............. : 2
-- Match limit ..................... : 10000000
-- Match limit recursion ........... : MATCH_LIMIT
-- Build shared libs ............... : ON
-- Build static libs ............... : OFF
-- Link pcregrep with libz ......... : ON
-- Link pcregrep with libbz2 ....... : None
-- Link pcretest with libreadline .. : None
-- Non-standard dll names (prefix) . : OFF
-- Non-standard dll names (suffix) . : OFF
--
-- Configuring done
-- Generating done
-- Build files have been written to: C:/Mudlet/pcre-7.8

User avatar
Vadi
Posts: 5042
Joined: Sat Mar 14, 2009 3:13 pm

Re: Compiling on windows

Post by Vadi »

Try using qmake; while I think cmake was updated recently, qmake is still what we use.

User avatar
tsuujin
Posts: 695
Joined: Fri Feb 26, 2010 12:59 am
Location: California
Contact:

Re: Compiling on windows

Post by tsuujin »

Still not having much luck here. I tried using qmake and was greeted with a large list of warnings on missing dependencies (which I can probably fix by properly configuring qmake, was complaining of things like missing fonts and so forth). When I drop out of the src directory and try to use cmake from the beta folder I actually get it to compile properly, but make install tells me it can't find the .exe to transfer. When I try to run the .exe from the src directory it complains about a missing .dll.

Going to work on it some more... then perhaps write us a new guide to compile on windows that's a bit more detailed if I get it to work.

User avatar
Vadi
Posts: 5042
Joined: Sat Mar 14, 2009 3:13 pm

Re: Compiling on windows

Post by Vadi »

Yeah. I'm not sure at this point, would need Heiko to pitch in.

User avatar
tsuujin
Posts: 695
Joined: Fri Feb 26, 2010 12:59 am
Location: California
Contact:

Re: Compiling on windows

Post by tsuujin »

In case this means anything to anyone, the error I'm getting when I try to run the exe is "The procedure entry point _Z11qt_assert_xPKcSO_SO_i could not be located in the dynamic link library QtCore4.dll."

User avatar
Vadi
Posts: 5042
Joined: Sat Mar 14, 2009 3:13 pm

Re: Compiling on windows

Post by Vadi »

That means you're using different Qt versions there

User avatar
tsuujin
Posts: 695
Joined: Fri Feb 26, 2010 12:59 am
Location: California
Contact:

Re: Compiling on windows

Post by tsuujin »

Ah, that would make sense wouldn't it. So do I have two different qt versions on my system, or have I simply installed the wrong one now? Actually, I think it may be the former. Worth looking into. Thanks!

User avatar
Vadi
Posts: 5042
Joined: Sat Mar 14, 2009 3:13 pm

Re: Compiling on windows

Post by Vadi »

Yeah, it would be two different ones that produce this.

User avatar
tsuujin
Posts: 695
Joined: Fri Feb 26, 2010 12:59 am
Location: California
Contact:

Re: Compiling on windows

Post by tsuujin »

It was actually just an error in the makefile that had to be corrected manually.

However... I think something is amiss. What is the current version of Mudlet? The About dialog claims that I'm running Beta 6, built in 2009...

User avatar
tsuujin
Posts: 695
Joined: Fri Feb 26, 2010 12:59 am
Location: California
Contact:

Re: Compiling on windows

Post by tsuujin »

Ok. Too many problems with the guide for compiling. I'm scrapping everything and starting fresh. Lets see if I can get some better results this time.

edit: wow, this is frustrating. I've tried a clean sweep, updated from the -correct- git version, and used the QT designer to run the build as I always did on Linux and I'm greeted with a large list of compile errors, spawning from the fact that the designer doesn't seem to care to look in my paths for files while compiling.

Post Reply