Shop OBEX P1 Docs P2 Docs Learn Events
PZST - an open-source Propeller IDE in development [ Version 1.0.1 released! ] - Page 7 — Parallax Forums

PZST - an open-source Propeller IDE in development [ Version 1.0.1 released! ]

123457

Comments

  • Andrey DemenevAndrey Demenev Posts: 377
    edited 2011-05-23 01:39
    src.pro contains the following:

    unix:!macx:INCLUDEPATH += /usr/lib/dbus-1.0/include
    unix:!macx:INCLUDEPATH += /usr/include/dbus-1.0

    so the genarated makefile should have these path in commands invoking c++ compiler. this is how it looks :

    g++ -c -pipe -g -pg -Wall -W -D_REENTRANT -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I../../../qtsdk-2010.01/qt/mkspecs/linux-g++ -I. -I../../../qtsdk-2010.01/qt/include/QtCore -I../../../qtsdk-2010.01/qt/include/QtGui -I../../../qtsdk-2010.01/qt/include -I/usr/lib/dbus-1.0/include -I/usr/include/dbus-1.0 -I. -I. -o eserialport_nonosx.o eserialport_nonosx.cpp

    It's a mystery why these paths from the project files are not in makefile
  • Andrey DemenevAndrey Demenev Posts: 377
    edited 2011-05-23 01:53
    First release is scheduled for June 1st - may be only deferred in case of things go wrong with OS X version.
  • Heater.Heater. Posts: 21,230
    edited 2011-05-23 02:28
    If I hack the include paths -I/usr/lib/dbus-1.0/include/ -I/usr/include/dbus-1.0 into the Makefile then eserialport_nonosx.cpp compiles.
    Then it proceeds to try and compile eserialport_osx.cpp.which of course fails due to the lack of IOKit.

    Looks like it has got confused between building for mac or unix.
    code
g++ -c -pipe -O2 -Wall -W -D_REENTRANT -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/lib/dbus-1.0/include/ -I/usr/include/dbus-1.0 -I/usr/share/qt4/mkspecs/linux-g++ -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -Isrc -IQsci -I. -I. -o eserialport_nonosx.o src/eserialport_nonosx.cpp
g++ -c -pipe -O2 -Wall -W -D_REENTRANT -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/lib/dbus-1.0/include/ -I/usr/include/dbus-1.0 -I/usr/share/qt4/mkspecs/linux-g++ -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -Isrc -IQsci -I. -I. -o eserialport_osx.o src/eserialport_osx.cpp
src/eserialport_osx.cpp:4:27: fatal error: IOKit/IOTypes.h: No such file or directory
  • Andrey DemenevAndrey Demenev Posts: 377
    edited 2011-05-23 02:47
    Are you using Qt tools from Debian packages repository?
  • Heater.Heater. Posts: 21,230
    edited 2011-05-23 04:11
    Might be. I have a newer Qt version installed as well. Have to wait till I get back home to verify that.
  • Andrey DemenevAndrey Demenev Posts: 377
    edited 2011-06-01 06:32
    Release is being delayed, I need more time for documentation
  • Andrey DemenevAndrey Demenev Posts: 377
    edited 2011-06-28 08:01
    Windows installer has been built. The impatient can download it from http://code.google.com/p/pzst/downloads/list. Others may wait until manual is released - I am making final touches to Russian text, then English translation will follow
  • BatangBatang Posts: 234
    edited 2011-06-28 08:55
    Hi Andrey,

    I just tried the windows version with the latest bstc and get the following error when compiling;

    bstc.exe illegal option -- q

    Cheers
  • yetiyeti Posts: 818
    edited 2011-06-28 09:08
    Batang wrote: »
    I just tried the windows version with the latest bstc and get the following error when compiling;

    bstc.exe illegal option -- q
    $ ./bst/bstc-0.15.3 | grep -- -q
$ ./bst/bstc-0.15.4-pre9 | grep -- -q
 -q            - Be silent except for GCC style errors and warnings
    ...means: bstc-0.15.3 has no -q option, bstc-0.15.4-pre9 has.
  • BatangBatang Posts: 234
    edited 2011-06-28 09:18
    Where is bstc-0.15.4-pre9 downloaded from?

    As http://www.fnarfbargle.com/bst/bstc/Latest/ does no have it.
  • SSteveSSteve Posts: 808
    edited 2011-06-28 09:23
    The pre-release versions are at http://www.fnarfbargle.com/bst/snapshots/
  • MacTuxLinMacTuxLin Posts: 821
    edited 2011-06-28 21:47
    Hello Andrey,
    Great IDE! Any possibility to change the background colors by sections like Propeller Tool?
  • Andrey DemenevAndrey Demenev Posts: 377
    edited 2011-06-28 21:51
    MacTuxLin: file a feature request at http://code.google.com/p/pzst/issues/list
  • MacTuxLinMacTuxLin Posts: 821
    edited 2011-06-29 00:24
    Thanks. Added but, its my first time using a google code request & I can't seems to change the wrong type from Defect to Feature Request...
  • Andrey DemenevAndrey Demenev Posts: 377
    edited 2011-07-20 03:45
    I've got permission from Brad Campbell to distribute bstc with PZST, so I will include version of bstc guaranteed to work, so no magic with file extensions, PATH etc will be required.

    Documentation translation to English is 40% done
  • Andrey DemenevAndrey Demenev Posts: 377
    edited 2011-08-07 23:02
    Okay, guys and gals :)

    Today I have released PZST version 1.0.1. Installation files for Windows and Debian and derivates (pronounced /uˈbuntuː/ :) ) are available for download from project's page on Google Code. Manuals in English and Russian are there as well.

    Unfortunately, I am not able to make a release for Mac OS X. SSteve was able to compile the software under OS X, and made an installer. But there is a a problem that makes PZST not usable. I believe this is an OS X specific issue, since I was unable to reproduce it under other OS

    Anyway, you all are welcome to try PZST. I am leaving today, and will be traveling the next couple of days. On return, I want to hear your opinions, and bug reports, of course :)

    For next release, I will be adding serial terminal. And then, project manager's turn, the first step to support languages other than SPIN (primarily PropBasic)
  • SapiehaSapieha Posts: 2,964
    edited 2011-08-08 00:07
    Hi Andrey.

    Installation function correctly on XP SP3 Swedish.

    Have You possibility to add Control of Colors -- As some colors You use are mostly unreadable for my eyes



    Andrey Demenev wrote: »
    Okay, guys and gals :)

    Today I have released PZST version 1.0.1. Installation files for Windows and Debian and derivates (pronounced /uˈbuntuː/ :) ) are available for download from project's page on Google Code. Manuals in English and Russian are there as well.

    Unfortunately, I am not able to make a release for Mac OS X. SSteve was able to compile the software under OS X, and made an installer. But there is a a problem that makes PZST not usable. I believe this is an OS X specific issue, since I was unable to reproduce it under other OS

    Anyway, you all are welcome to try PZST. I am leaving today, and will be traveling the next couple of days. On return, I want to hear your opinions, and bug reports, of course :)

    For next release, I will be adding serial terminal. And then, project manager's turn, the first step to support languages other than SPIN (primarily PropBasic)
  • SSteveSSteve Posts: 808
    edited 2011-08-08 11:38
    Andrey Demenev wrote: »
    Unfortunately, I am not able to make a release for Mac OS X. SSteve was able to compile the software under OS X, and made an installer. But there is a a problem that makes PZST not usable. I believe this is an OS X specific issue, since I was unable to reproduce it under other OS

    I wouldn't say it make PZST unusable. It's a little annoying, but can be ignored. I will try to work on making an installer, but I might not be able to get to it before the weekend.
  • JonnyMacJonnyMac Posts: 9,108
    edited 2011-08-09 07:35
    Have You possibility to add Control of Colors -- As some colors You use are mostly unreadable for my eyes

    I, too, would like the ability to change the syntax highlighting colors. Most are just fine, a couple, though, I'd love to change.

    Nicely done, BTW. I'm sorry I didn't know about this before doing my Propeller presentation at DefCon over the weekend.
  • Heater.Heater. Posts: 21,230
    edited 2011-08-09 08:47
    Just fired up the debian version from the command line. Every time I hit a key in the editor it spits out a message to the terminal "QFileSystemWatcher: failed to add paths: /home/bla/bla..."
  • Andrey DemenevAndrey Demenev Posts: 377
    edited 2011-08-09 17:29
    Sapieha wrote: »
    Have You possibility to add Control of Colors -- As some colors You use are mostly unreadable for my eyes
    Heater. wrote: »
    Just fired up the debian version from the command line. Every time I hit a key in the editor it spits out a message to the terminal "QFileSystemWatcher: failed to add paths: /home/bla/bla..."

    Thanks for feedback, I've added these two to issues tracker.
  • Andrey DemenevAndrey Demenev Posts: 377
    edited 2011-08-09 17:33
    SSteve wrote: »
    I wouldn't say it make PZST unusable. It's a little annoying, but can be ignored. I will try to work on making an installer, but I might not be able to get to it before the weekend.

    OK, let's move that way. Remember that bstc can be distributed with PZST to simplify the installation process - do that for both Windows installer and Debian package. Rename bstc.osx to bstc.pzst, and make the installer to place that file to same directory where pzst executable is installed.
  • Kit MortonKit Morton Posts: 39
    edited 2011-08-09 23:02
    I just wanted to say thank you and great job on PZST. I just tried it for the first time and it is the first SPIN IDE I've used that really feels like a fully fledged IDE. One request though, would it be possible to for you to make a x64 linux package. It's not that hard to compile, but it would be convenient. I would try my hand at it, but I've never tried to package any software.

    -Kit
  • Andrey DemenevAndrey Demenev Posts: 377
    edited 2011-08-10 00:55
    I've never used 64-bit systems. Would a binary compiled for 32-bit system work on 64 bit machine? I think bstc (the actual compiler used) is only available as 32-bit executable.
  • TorTor Posts: 2,010
    edited 2011-08-10 01:25
    Andrey Demenev wrote: »
    I've never used 64-bit systems. Would a binary compiled for 32-bit system work on 64 bit machine? I think bstc (the actual compiler used) is only available as 32-bit executable.
    We're talking Linux here, right? There shouldn't be any problems.

    >file /usr/local/bin/bstc
    /usr/local/bin/bstc: ELF 32-bit LSB executable, Intel 80386, version 1 (GNU/Linux), statically linked, stripped

    >uname -rs
    Linux 2.6.39-1-amd64

    Edit: After reading Heater's post I think you weren't really asking about bstc.. and yes, 32-bit Qt apps should work on 64-bit Linux systems, as long as you use a 64-distribution which provides the 32-bit versions of the dynamic shared libraries (because your Qt application will not be a static, simpler app like bstc). Debian, as Heater refers to, is one of those distros with a good working 32+64-bit setup.


    -Tor
  • Heater.Heater. Posts: 21,230
    edited 2011-08-10 01:27
    I have just been building Qt apps on a 64 bit Debian (Lenny) and was surprised to see that the resulting executables were 32 bit. Turns out the Qt libs there are 32 bit.
    So a 32 bit build should run there. No idea if you have to do anything special to create the package though.
  • Kevin WoodKevin Wood Posts: 1,266
    edited 2011-08-10 02:19
    Andrey Demenev wrote:
    I've never used 64-bit systems. Would a binary compiled for 32-bit system work on 64 bit machine? I think bstc (the actual compiler used) is only available as 32-bit executable

    32-bit bianries should work provided that the correct 32-bit libraries are installed. You can check by running the command ldd <binary>. You'll get a listing of dependencies needed. Any that aren't installed can usually be found in the repos.
  • Kit MortonKit Morton Posts: 39
    edited 2011-08-10 18:58
    The binaries may work, I'm not sure, but the package won't install. Xubuntu, the distro I'm using, won't install the package because it see's that it's a 32 bit package.
  • Kevin WoodKevin Wood Posts: 1,266
    edited 2011-08-10 19:50
    Kit, you can extract the .deb file (do it in a separate folder), then the 2 other archives in the .deb. This will give you a usr directory that you can cd into, and run the ldd command against the pzst binary. If nothing is missing, just try running the binary. If it runs, you can just copy the binaries to whatever folder and run them from there.
  • TorTor Posts: 2,010
    edited 2011-08-11 01:01
    And if that works out OK it's easy to repack a new .deb from the unpacked .deb and label the new one as 64-bit, then install as usual.

    -Tor
Sign In or Register to comment.