can't build on ArchLinux 64

[Google Code Exporter]

What steps will reproduce the problem?
1../configure --prefix=/usr
2.
3.

What is the expected output? What do you see instead?
to build. 
 ./configure --prefix=/usr 
Traceback (most recent call last):
  File "./configure", line 208, in <module>
    main()
  File "./configure", line 164, in main
    join(getTemplatesDirectory(), "config.h"), data)
  File "/home/harv/synthclone-0.3.0/install/util.py", line 66, in writeTemplate
    fp = file(source)
NameError: global name 'file' is not defined

What version of the product are you using? On what operating system?
synthclone-0.3.0
 ArchLinux 64

Please provide any additional information below.

when using the PKGBUILD format that Arch uses, I get this error:
==> Making package: synthclone 0.3.0-1 (Sat Sep 14 12:02:01 EDT 2013)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found synthclone-0.3.0.tar.gz
==> Validating source files with md5sums...
    synthclone-0.3.0.tar.gz ... Passed
==> Extracting sources...
  -> Extracting synthclone-0.3.0.tar.gz with bsdtar
==> Removing existing pkg/ directory...
==> Starting build()...
Reading 
/tmp/packerbuild-1000/synthclone/synthclone/src/synthclone-0.3.0/src/src.pro
 Reading /tmp/packerbuild-1000/synthclone/synthclone/src/synthclone-0.3.0/src/lib/lib.pro
Project WARNING: CONFIG+=uitools is deprecated. Use QT+=uitools instead.
Project ERROR: Unknown module(s) in QT: uitools
Usage: configure [options] [qmake-args]

configure: error: qmake returned an error
==> ERROR: A failure occurred in build().
    Aborting...
The build failed.

when building from source, I get this error:

./configure --prefix=/usr 
Traceback (most recent call last):
  File "./configure", line 208, in <module>
    main()
  File "./configure", line 164, in main
    join(getTemplatesDirectory(), "config.h"), data)
  File "/home/harv/synthclone-0.3.0/install/util.py", line 66, in writeTemplate
    fp = file(source)
NameError: global name 'file' is not defined

Original issue reported on code.google.com by [e-mail] on 14 Sep 2013 at 4:13

[Google Code Exporter]

What versions of python and Qt are installed on your system?

Original comment by [e-mail] on 14 Sep 2013 at 8:56

[Google Code Exporter]

python-3.3.2
python2-2.7.5
qt4
qt5

Original comment by [e-mail] on 14 Sep 2013 at 9:56

[Google Code Exporter]

I just committed a change that allows synthclone to be built when the default 
Python interpreter is a Python 3 interpreter (which I think it is, in your 
case).  This should take care of the "'file' is not defined" errors.

The uitools error is a bit more complex.  A bit of research tells me that this 
is an issue when trying to build a Qt 4 application (like synthclone) against 
Qt 5.  I haven't started porting synthclone to Qt 5 yet, so I don't expect this 
to work.  I suggest you get in touch with the package maintainer and make sure 
that synthclone is explicitly linking against Qt 4.  There may also be 
something I can do on my end to make things work properly.  Not sure.

I'm going to keep this issue open for now, as it will serve as a reminder that 
I have to get around to porting synthclone to Qt 5.

Please let me know if the change solves your problem.

Thanks. :)

Original comment by [e-mail] on 14 Sep 2013 at 10:52

• Changed state: Started

[Google Code Exporter]

you're right, must be the Qt5:

./configure --prefix=/usr 
Reading /home/harv/synthclone/src/src.pro
 Reading /home/harv/synthclone/src/lib/lib.pro
Project WARNING: CONFIG+=uitools is deprecated. Use QT+=uitools instead.
Project ERROR: Unknown module(s) in QT: uitools
Usage: configure [options] [qmake-args]

configure: error: qmake returned an error

Original comment by [e-mail] on 15 Sep 2013 at 1:22

[Google Code Exporter]

I did a little research, and found that ArchLinux adds symlinks to different 
qmakes for different Qt versions installed on your system.  Some info can be 
found here:

    https://wiki.archlinux.org/index.php/Qt

I added a switch to the configure script that allows you to specify the 
location of the qmake executable you want to use.  So, this might work:

    ./configure --prefix=/usr --qmake=qmake-qt4

Let me know if this works for you.

Original comment by [e-mail] on 15 Sep 2013 at 11:44

[Google Code Exporter]

nope, didn't work:

./configure --prefix=/usr --qmake=qmake-qt4
Usage: configure [options] [qmake-args]

configure: error: no such option: --qmake

Original comment by [e-mail] on 16 Sep 2013 at 12:59

[Google Code Exporter]

Are you checking out the source from the git repository?  Make sure you 
checkout the source from git:

    git clone https://code.google.com/p/synthclone/

Original comment by [e-mail] on 16 Sep 2013 at 1:06

[Google Code Exporter]

I should have specified the source checkout earlier instead of assuming that 
you had already checked out the source.  Sorry about that.

Original comment by [e-mail] on 16 Sep 2013 at 1:10

[Google Code Exporter]

yep I did yesterday but not the first try today.. I just did a fresh pull:

 ./configure --prefix=/usr --qmake=qmake-qt4
  File "./configure", line 213
    except Exception, e:
                    ^
SyntaxError: invalid syntax

Original comment by [e-mail] on 16 Sep 2013 at 1:12

[Google Code Exporter]

Yikes!  Another Python 3 incompatibility.  Sorry about that.  Just fixed it in 
trunk.

Original comment by [e-mail] on 16 Sep 2013 at 1:22

[Google Code Exporter]

bingo!! worked. it built fine.. thanx man!

Original comment by [e-mail] on 16 Sep 2013 at 1:50

[Google Code Exporter]

You're welcome!  Thanks for your patience.  I'm going to close this bug, and 
open another for porting to Qt5.

I hope you enjoy using synthclone.  Let me know if you run into any more issues.

Original comment by [e-mail] on 16 Sep 2013 at 1:51

• Changed state: Fixed

[Google Code Exporter]

I've always loved this app. 

Original comment by [e-mail] on 16 Sep 2013 at 1:54

[Google Code Exporter]

Oh!  Fantastic.  Have you released any music that contains synthcloned 
instruments? :)

Original comment by [e-mail] on 16 Sep 2013 at 2:11

[Google Code Exporter]

I've been ripping sf2 drumkits for Hydrogen.. Haven't tried any synths yet.. I 
made music of course with the kits.. no releases yet.

Original comment by [e-mail] on 16 Sep 2013 at 2:35