Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

autogen.py fails on windows (no module named cpack) #25

Closed
bornschein opened this issue Apr 3, 2013 · 6 comments
Closed

autogen.py fails on windows (no module named cpack) #25

bornschein opened this issue Apr 3, 2013 · 6 comments

Comments

@bornschein
Copy link

I am doing this:

git clone https://github.com/KDAB/KDSoap.git
cd KDSoap
git submodule update --init
set PATH=%PATH%;C:\Qt\qt-5.0.1\qtbase\bin
autogen.py

... and get the following error trace:

Traceback (most recent call last):
File "C:\Qt\KDSoap\autogen.py", line 2, in
from autogen.autogen import autogen
File "C:\Qt\KDSoap\autogen\autogen.py", line 3, in
from cpack import CPackGenerateConfiguration
ImportError: No module named 'cpack'

@winterz
Copy link
Member

winterz commented Apr 3, 2013

a few things to check:
which python? could you be finding a python inside cygwin or msys somehow?
%PYTHONPATH% . is that set properly?
git . did the files in the autogen subdir get checkout properly? do they have CRLF line-endings?

so make sure you have kdsoap/autogen/cmake.py and it looks ok and has CRLF line-endings and PYTHONPATH isn't messed-up somehow. and make sure your python is the right one.

then, if all that looks ok... possibly we need to look at setting your PYTHONPATH to C:\Qt\KDSoap\autogen

@winterz winterz closed this as completed Apr 3, 2013
@winterz winterz reopened this Apr 3, 2013
@winterz
Copy link
Member

winterz commented Apr 3, 2013

oops. reopening

@bornschein
Copy link
Author

Hi Allen,

Here is the deal:
We have 2 different windows 7 machines, both with Qt 5.0.1.
On machine 1 KDSoap builds just fine.
On machine 2 we cannot get autogen to run properly with the original mentioned error trace .

In order to eliminate git differences (crlf and stuff like this) I even zipped and copied the whole KDSoap directory from machine 1 to machine 2.
But autogen still fails on machine 2 and still passes on machine 1.

On both machines there is no %PYTHONPATH% set. This seems not to be necessary since machine 1 builds fine. Python itself is in the PATH
On both machines there is also no kdsoap/autogen/cmake.py file

We use python 3.3

Any other idea?

Thanks
Stefan

From: Allen Winter [mailto:notifications@github.com]
Sent: Thursday, April 04, 2013 1:08
To: KDAB/KDSoap
Cc: Stefan Bornschein
Subject: Re: [KDSoap] autogen.py fails on windows (no module named cpack) (#25)

a few things to check:
which python? could you be finding a python inside cygwin or msys somehow?
%PYTHONPATH% . is that set properly?
git . did the files in the autogen subdir get checkout properly? do they have CRLF line-endings?

so make sure you have kdsoap/autogen/cmake.py and it looks ok and has CRLF line-endings and PYTHONPATH isn't messed-up somehow. and make sure your python is the right one.

then, if all that looks ok... possibly we need to look at setting your PYTHONPATH to C:\Qt\KDSoap\autogen


Reply to this email directly or view it on GitHubhttps://github.com//issues/25#issuecomment-15871132.

@winterz
Copy link
Member

winterz commented Apr 4, 2013

Stefan,
confirmed. I can duplicate the problem with python3.
in the meantime, while I try to fix, you could try python2.7

@winterz
Copy link
Member

winterz commented Apr 7, 2013

Stefan, please make sure to use python2. The autogen program is not ported to Python3 yet. We are discussing supporting Python3 but haven't made a decision yet.

For now, I will close this.

@winterz winterz closed this as completed Apr 7, 2013
@Chadster766
Copy link

This is happening on a Debian Linux dev platform if I checkout any of the tags but not if I build trunk.

Should I run trunk? I don't normally do that for development.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants