I want to develop pys60 by eric4 IDE. I know that it's so late and has no worth but I need it. The following link:
http://developer.nokia.com/Community/Discussion/showthread.php/173353-Eric-Ide-perfect-IDE-for-Python-PyS60-developmant
describes it completely. I do all step. Step 7 and 8 is done by typing following codes in command line:
python C:\Python27\Lib\site-packages\eric4\eric4-api.py -o C:\PyS60_api.api -R -p “C:\Program Files\PythonForS60\module-repo”
python C:\Python27\Lib\site-packages\eric4\eric4-api.py -o python_api.api -R -p C:\Python27
python C:\Python27\Lib\site-packages\eric4\eric4-api.py -o eric_pyqt.api -R -p C:\Python27\Lib\site-packages\PyQt4
after this, “PyS60_api.api” file is created at “C:\” and “eric_pyqt.api”, “python_api.api” files are created at “C:\Windows\System32″. I add them to eric IDE by using ” Settings -> Preference-> editor ->APIs”, then compile and apply.
So I think that I had done all steps correctly. But I have a big problem. eric IDE does not know pys60 modules, for ex, appuifw, e32, camera, … . In other words, if I type
import camera
in eric IDE shell, then I have this error:
Traceback (innermost last):
File “”, line 1, in
ImportError: No module named camera
I have Windows 8.
Your best bet is using S60v3 FP1/FP2 SDK. Really it is the only way to develop and test PyS60 app on PC. You will need:
Nokia S60v3 FP1/FP2 SDK
Python 2.0.0 SDK (FP1 or FP2 accordingly) for Nokia
OpenC 3.0 SDK plugin
Related
Im just starting with cocos2d-x. I start by following the guide here. https://docs.cocos2d-x.org/cocos2d-x/v4/en/installation/Windows.html
Regarding prerequisites:
Windows 7+ - have windows 10
VS 2017+ - have visual studio 2019
CMake 3.1+ - installed latest
Python 2.7.5+, Python 2.7.10 reccomended , NOT Python 3+ - installed Python 2.7.10
Downloaded Cocos2dx v4 from github repo.
I run this command
python setup.py
https://i.imgur.com/td7Yo8c.png
Then i run this command
cd COCOS2DX/tests/cpp-tests
mkdir win32-build
cd win32-build
cmake ..
Then I rebuild the generated solution and get this error.
https://i.imgur.com/bZ8QUZF.png
Please advise.
Thanks.
use cmake .. -G"Visual Studio 16 2019" -Tv142 -A Win32
I can't quite make out details in picture, but you have failure accessing the Cocos library.
I got Cocos2d-x 3.17.2 working on VS2017 for cpp-test on Win10.
The generated Win32 solution for some reason did not include the cocos library.
I had to manually include libcocos2d, librecast, and libSpine projects in solution, fix dependencies and add libcocos2d resource to cpp-test project to make it compile.
As an aside, I am finding the test code quite helpful for showing how to accomplish things - just find a test doing what you are trying to do, and examine / step through the code to see how.
If you still have problems, perhaps ask for help on the Cocos2d-x forum:
https://discuss.cocos2d-x.org/
I'm trying to setup my first development for esp32 with eclipse on windows 7.
I installed esp-idf using esp-idf-tools-setup.exe installer which should install
everything needed.
I'm testing with the hello world example app from esp-idf. I can compile it using the python command line
idf.py build
But I need eclipse, it's a bit less obvious... I followed these instructions:
In this page, I can see that there's a need of msys. So I installed
msys2 64 bits.
I copied the xtensa-esp32-elf dir into the "msys64\var\opt" directory to match the PATH variable (and updated it based on the documentation)
Now, when compiling with eclipse, I got the following error:
Traceback (most recent call last):
File "C:/program/esp-idf/tools/windows/eclipse_make.py", line 36, in <module>
main()
File "C:/program/esp-idf/tools/windows/eclipse_make.py", line 29, in main
make = subprocess.Popen(["make"] + sys.argv[1:] + ["BATCH_BUILD=1"], stdout=subprocess.PIPE)
File "C:\python27\lib\subprocess.py", line 390, in __init__
errread, errwrite)
File "C:\python27\lib\subprocess.py", line 640, in _execute_child
startupinfo)
WindowsError: [Error 2] Le fichier spécifié est introuvable
Python make is unable to launch "make". The thing is I can't find a make exe anywhere...
This other page states that I must run
make menuconfig
before building with eclipse but, of course, this does not work better for the same reason...
What should I do?
Well, in windows you have nmake (IIRC installed with visual studio tools - or the free where vstools compiler pack). Or you can install something more like gnu-make from one of:
mingw32 : link
cygwin : link
msys2 : link
gnuwin32 : link
There are others as well. Some of these have make command (if you add the bin folder to your path) others will have things like mingw32-make which you may have to alias (I made a batch file called make.bat which just calls mingw32-make %*. But where ever you install make (and nmake IMHO is a really limited poor version of make) you need to add it to your windows path before you run your python script. So in short I think you are just missing a set of tools...
Another option is to just copy ...\MinGW\bin\mingw32-make.exe to ...\MinGW\bin\make.exe
I did add mys2 thinking it will contain everything needed.
In fact msys2 is delivered with a very minimal set of features. I had to install make using the msys2 package manager with the following command:
pacman -S make
Pretty simple when you know!
For esp-idf cmake projects, try this https://github.com/espressif/idf-eclipse-plugin
I am trying to compile my python 3.5 file with the latest py2exe version 0.9.2.2 with the following command:
py -3.5 -m py2exe.build_exe myscript.py
But it reports this:
"run-py3.5-win-amd64.exe" file is not found in the
...lib\site-packages\py2exe\ folder.
Does this mean that py2exe 0.9.2.2 is only compatible up to python 3.4?
Unfortunately as of November 2016 there is still no Python 3.5 support in sight for py2exe. However, I've had great success using cx_Freeze 5.0 with Python 3.5 and since both projects use a very similar configuration I've migrated away from py2exe to cx_Freeze without much work. Binary Wheels of cx_Freeze 5.0 for Python 3.5 are now available officially on PyPi: https://pypi.python.org/pypi/cx_Freeze
Install pyinstaller through Command Prompt (Microsoft Windows) :
search cmd on windows to open Command Prompt with black screen
type and enter: pip install pyinstaller
Again at Command Prompt type and enter: cd c:\....(the Folder where your file example.py is located)
Finally type and enter: pyinstaller --onefile example.py
Now after some minutes your example.exe is ready
There are significant changes in Python 3.5 regarding the MSVCR dll dependency. py2exe 0.9.2.2 supports Python 3.3 and 3.4
Article describing these changes - BUILDING EXTENSIONS FOR PYTHON 3.5
I came here looking for a 3.5 exe generator. I've found that using "pyinstaller" version 3.2 works perfectly with python 35. I found the easiest way to use it is from the command window when on Windows. To make things a little easier you can create a command window from the directory your scripts are stored. Here's how:
From the directory your scripts are saved you can launch a command window by holding 'Alt' + 'Shift' and clicking on the window. In the drop down menu you will see "Open Command Window Here". In that command window you will write 'pyinstaller --onefile script.py' where "script.py" is the name of the script you want to generate the .exe for. I hope this helps someone else as much as it helped me.
Py2Exe just released Py2Exe for Python 3!
To install on windows do this:
cd C:\Python34\Scripts
Then run:
pip install py2exe
And your done you can now run the normal commands, and if your having trouble here are the docs.
I note that the original question was asked just shy of 4 years ago. Visiting https://pypi.org/project/py2exe/
the version offered is still at 0.9.2.2
Using the command pip install py2exe and checking the py2exe directory created on my system, I only see options for Python 3.3 and 3.4 installed.
Given that the last time py2exe was updated was in 2014, my guess is that it is no longer being developed so folks wanting to create executables using versions of Python more recent than 3.4 should look elsewhere for a solution.
**
#I use pyinstaller
#pip install pyinstaller
#command line:
#pyinstaller --onedir --onefile --name=what you call it --console myscript.py
#pyinstaller --onedir --onefile --name=what you call it --windowed myscript.py
#pyinstaller -h help file
#pyinstaller -d -f -n=file name -c or -w myscript.py
**
There is py2exe for python versions that can be downloaded at https://pypi.python.org/pypi/py2exe/0.9.2.0#downloads
I am trying to build OpenCASCADE on Mac, but I am not having any luck.
I downloaded it from Github in tar.gz, but I am really new to Mac and I am stuck.
Can anybody explain what should be my next step?
(I found some terminal commands what I should use, but I am not familiar with them. So if it is the right way to build OpenCASCADE on Mac please write down the terminal commands with details. Thank you!)
EDIT:
I understood the command line commands now from the link below. I understood it before too, but I was mistaken, because my main problem was, that I didn't had gcc installed (XCode does not installs gcc automatically...). So anyways, now finally I can run the cmake command. It starts but it ends with this:
CMake Error at /Applications/CMake
2.8-9.app/Contents/share/cmake-2.8/Modules/FindX11.cmake:420 (MESSAGE): Could not find X11 Call Stack (most recent call first):
CMakeLists.txt:313 (FIND_PACKAGE)
Anybody have any idea what to do? I tryed to search this too here, and google...and I found some "solutions" but those didn't work for me.
EDIT EDIT:
The solution for the last edit is that Mountain Lion doesn't install X11. So open up an app that uses X11 or Xquartz and it will install automatically.
Unfortunetly it still doesn't work. My next error message is the following after the make command in terminal:
In file included from
/Users/davidbirkas/Documents/tpaviot-oce-6c9a06a/src/AlienImage/AlienImage_X11XWDAlienData.cxx:14:
/Users/davidbirkas/Documents/tpaviot-oce-6c9a06a/inc/Aspect_XWD.hxx:5:12:
fatal error:
'X11/XWDFile.h' file not found
# include
^ 1 error generated. make[2]: * [adm/cmake/TKService/CMakeFiles/TKService.dir/_/_/__/src/AlienImage/AlienImage_X11XWDAlienData.cxx.o]
Error 1 make1:
[adm/cmake/TKService/CMakeFiles/TKService.dir/all] Error 2 make: **
[all] Error 2
Any ideas how to fix this?
Ensure that, together with XCode, you also install the X11 support from Apple's Devtools. Your error message is indicating that it is missing.
FWIW, I have written a blog post about OCC and PythonOCC on Mac some time ago. Maybe you'll find some detailed info there.
http://cad-3d.blogspot.com/2011/10/pythonocc-open-source-interactive-cad.html
In this post, I still talk about using the binary installer, but recent updates to the OCE edition compile usually without problems out-of-the-box, also on OSX (that is NOT the case with the official OpenCASCADE release).
I spent a little time on this and I think I have it. Here is what I did step by step:
Preparation phase:
Installing Xcode (with command line tools) = Apple developer site
// If Xcode doesn't install gcc, than you can still download it from the developer site as Command Line Tools for Xcode.
Installing Cmake (with command line tools) = Google
// You can download it from the official site with a .dmg/.pkg file extension. Easy install.
X11 under Mountain Lion "changed" to Xquartz. Probably it is not installed by default, but it is easy to check it. Just go to the folder "Application" and start the X11 app. If X11/Xquartz is not installed than it will install automatically!
Installing FTGL = MacPorts = Google
// Download MacPorts from their official site, install it with the installer, than write this to the terminal:
sudo port install ftgl
Download OCE and extract it (.OCE-0.9.0.tar.gz file) = https://github.com/tpaviot/oce/wiki/Download
Installing phase:
I. Open Terminal.
II. Run this command
// This will set the proper PATH.
ln -s /opt/X11/include/X11 /usr/local/include/X11
III. Than from the Terminal go to the directory where you extracted the OCE file (the original extracted file name should be: tpaviot-oce-6c9a06a).
IV. Than write these commands:
// You make a build directory to the extracted OCE folder.
mkdir build
cd build
V. After this you give out the cmake command:
cmake -DOCE_INSTALL_PREFIX:PATH=$HOME/OCE \
-DOCE_WITH_FREEIMAGE:BOOL=ON \
-DOCE_WITH_GL2PS:BOOL=ON \
-DOCE_DRAW:BOOL=ON \
..
VI. And at the end the make commands:
make
make install/strip
If you did everything exactly like this, than it should work!
Give OCE a try. Compiling for osx is a walk in the park
I'm developing some cross platform software targeting Mono under Visual Studio and would like to be able to build the installers for Windows and Linux (Ubuntu specifically) with a single button click. I figure I could do it by calling cygwin from a post-build event, but I was hoping for at best a Visual Studio plugin or at worst a more Windows-native way of doing it. It seems like the package format is fairly simple and this must be a common need.
edit: Re-asked question under other account due to duplicate login issue.
Debian's .deb packages are just "ar" archives containing tarballs. You can manipulate both types of files using cygwin or msys quite easily:
$ ar xv asciidoc_8.2.1-2_all.deb
x - debian-binary
x - control.tar.gz
x - data.tar.gz
$ tar -tzf control.tar.gz
./
./conffiles
./md5sums
./control
Or you can install all the "standard" Debian stuff using cygwin, I suppose, but most of that stuff won't benefit you much if you're building a .Net app anyway.
If you use the .NET Core SDK, you can use dotnet-packaging tools to create a Debian installer package from any platform that runs .NET Core.
For example, running dotnet deb -c Release -f netcoreapp2.1 -r ubuntu.16.04-x64 would then create a .deb file which you can use to install your app on Ubuntu 16.04.
The project repository has more details.
I am not aware of any plugin that does it natively, especially since Mono users seem to prefer MonoDevelop.
However, it should be possible to use Cygwin and a custom MSBuild Task or Batch file in order to achieve that by using the native .deb creation tools.
this must be a common need.
Some small percentage of software developers develop for .NET
Some very small percentage of that group develop for mono
Some small percentage of that group wants to provide .debs instead of just a zip
Some very small percentage of that group wants to build their linux apps on windows instead of natively on linux
It's just you :-)
If you don't mind using Java tools it's possible to build Debian packages with jdeb in an Ant script. That's probably lighter than relying on Cygwin.