Error building v3: JsonRideFile_yacc.h and y.tab.h files not found

[Ste]

Good afternoon,
I've a problem building v3 on windows xp.
After doing all the changes in the configuration files, almost
everything compiles well but I have the following problem when
arriving at the yacc files:

mingw32-make -f Makefile.Release
cd src\ && mingw32-make release
mingw32-make[1]: Entering directory `D:/Coding/GCV3z/src'
mingw32-make -f Makefile.Release
mingw32-make[2]: Entering directory `D:/Coding/GCV3z/src'
D:/Dati/ag71481/Coding/Bison/bin/bison --file-prefix=y -t -d -p
JsonRideFile Jso
nRideFile.y
del JsonRideFile_yacc.h JsonRideFile_yacc.cpp
File not found D:\Dati\ag71481\Coding\GCV3z\src\JsonRideFile_yacc.h
move y.tab.h JsonRideFile_yacc.h
process_begin: CreateProcess(NULL, move y.tab.h
JsonRideFile_yacc.h, ...) failed
.
make (e=2): File not found.
mingw32-make[2]: *** [JsonRideFile_yacc.h] Error 2
mingw32-make[2]: Leaving directory `D:/Dati/ag71481/Coding/GCV3z/src'
mingw32-make[1]: *** [release] Error 2
mingw32-make[1]: Leaving directory `D:/Dati/ag71481/Coding/GCV3z/src'
mingw32-make: *** [sub-src-sub_Release] Error 2

Looking around I cannot find neither y.tab.h nor JsonRideFile_yacc.h.

Could you please help?

Ciao,
Stefano

[Mark Liversedge]

The "del" command is returning an error code when asked to delete a
non-existant file, fortunately you can tell make/qmake to use another
command for file deletion.

I found that under mingw I needed to add the following to my
gcconfig.pri
QMAKE_YACC = "/ ... pathtobison... /bison --file-prefix=y -t"
QMAKE_LEX = "/ ... pathtoflex ... /flex"
QMAKE_DEL_FILE = rm -f

The clincher seemed to be QMAKE_DEL_FILE, since that is the error you
are seeing, but it wouldn't hurt to add the YACC and LEX lines either
obviously replacing the ... pathtoxxx... with the correct paths for
your install.

Regards,
Mark

[Gareth]

Actually Mark it is "move" that is failing. I don't know why this is
as it works fine.

I have the following in my gcconfig.pri

QMAKE_MOVE = copy

Which then copies the file over and it will compile.

[Ste]

Yapp!
That also fixed my error.
So, now everything compiles smoothly.

I executed GoldenCheetah from the release directory and... Mark, I
love the new interface!

Only one problem: when trying to build the installer,
GoldenCheetahInstall.nsi looks for two files that don't exist:

File "..\release\QxtCore.dll"
File "..\release\QxtGui.dll"

Am I missing something?
Forgive me... it's only the first week of (part-time) blindly
compiling GC...

Regards,
Stefano

[Mark Liversedge]

You need to copy them into the release directory from the Qt dist.
Also, if you are building with ical support the .nsi doesn't currently
include libical.dll. Will fix that at the weekend.

[Ste]

Mmmm, I've installed Qt in win XP starting from qt-sdk-win-
opensource-2010.05.exe and it seems I do not have any of the files
QxtCore.dll and QxtGui.dll in the Qt directories.
Is qt-sdk-win-opensource-2010.05.exe not the right file to start from
or am I doing something wrong?

Thanx,
Stefano

[Ste]

Ok,
I installed qXt starting from libqxt-v0.6.1.zip from
http://dev.libqxt.org/libqxt/get/v0.6.1.zip, compiled it and now I
have the two files...
Stefano

[Mark Liversedge]

Oh crap.

Sorry.

I didn't look closely enough at your original post.

Those two lines are a mistake!! To run you do not need the Qxt
Libraries. (Actually its 4 lines, 2 to install and 2 to uninstall)

I will fix up the .nsi file and push a patch.

Regards,
Mark

[Ste]

Ah ok, no problem...

By the way, do you know if there is a binary version of libical for
windows since I am getting strange errors when compiling it?

Ciao,
Stefano

[Mark Liversedge]

Gareth found them and sent me this... its what I use on Windows:

> I've tried to get the 0.46 version to compile but it is failing
> miserably. Hence I go to plan B which says go here:
> http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/ and
> download the precompiled versions (libical_0.43-1_win32.zip and
> libical-dev_0.43-1_win32.zip) and drop them in the MINGW directory of
> QT SDK and it should be good to go.

[Gareth]

libical binaries (0.43)

http://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/

Download the precompiled versions (libical_0.43-1_win32.zip and

libical-dev_0.43-1_win32.zip) and drop them in the MINGW directory of

QT SDK and you should be good to go.

O anywhere you want and then link as appropriate.

[Ste]

Thanx,
I did it and everything went fine.

I enjoyed the new gui and the new features for a while and then... the
idiot that is in me pushed and pushed.
So: I've lost a lot of time trying to build the kml capability.
I installed Visual Studio 2005 Express, compiled kml, etc. etc.
After a few attempts I decided that I can do without kml.

I recompiled everything without any problem (I am becoming skilled at
setting paths) but... when I run the executable from the release
directory I get the following error message (translated from italian):

Impossible to start the selected software. QtCore4.dll not found. A
new installation could solve the problem.

Well, QtCore4.dll is there, in the release directory (and in many
other places).
I've tried to uninstall and reinstall Qt as well as recompiling GC
several times without solving the problem.

Any help is really appreciated.

Ciao,
Stefano

[Ste]

Just to add information...
I've also built and run version2 without any prolem...

[Mark Liversedge]

On Jan 17, 2:48 pm, Ste <mantica.stef...@gmail.com> wrote:
> Just to add information...

> I've also built and run version2 without any problem...

Just to understand - are you saying that you have built v2 with KML
support and all is fine, but v3branch with KML support pops up the
QtCore4.dll error message?

If you have a working libkml.dll I'm sure gareth would bite your hand
off to push out a v2 build with KML support!!!

Cheers,
Mark

[Ste]

No, no, it's my fault, I wasn't clear enough.

I've never tried to build v2 with kml.

I was able to compile the 5 or 6 libraries in the kml distribution in
debug mode but I had compiler memory allocation errors in release
mode. I tried several /Zm factors but none worked and I gave up.

Then, I tried to build again v3 without kml and all sorts of error
messages came out. (I think Visual Studio was changing the definition
of Mingw commands; e.g. CC != gcc, ...).

So, I uninstalled Visual Studio 2005 Express and deleted all the kml
directories (with all the dlls).

Next, I have "successfully" built v2 and v3 without kml.
v2 works properly but v3 pops up the QtCore4.dll error message.

Quite annoying...

Ciao,
Stefano

[Gareth]

On Jan 12, 10:36 am, Gareth <garethc...@gmail.com> wrote:
> Actually Mark it is "move" that is failing. I don't know why this is
> as it works fine.

Actually, the better solution is this:

QMAKE_MOVE = cmd /c move

Mark:

Would it be a good idea to make gccconfig.pri.in look like

# let us know where flex/bison are:
#QMAKE_LEX = flex
#QMAKE_YACC = bison
#win32 {
# QMAKE_YACC = bison --file-prefix=y -t
# QMAKE_MOVE = cmd /c move
#}