pbp and linux

[Chirpy]

ok, I just tried it with Skin=None and the skins are still there, and it still is the same way. I dont think it's going to run on linux/wine. I think the only alternative is recompiling using freepascal, which I did look into it and it does open up those xe3 files, also it cross compiles to windows/linux/osx x86.

[mackrackit]

I just tried FineLine on my openSUSE box and did not have the refreshing problem but the menue bar was invisible.

Also tried installing PBP3 and did not have any luck due to the activation process. I did not play with it too much though, I am sure that there is a way...

So I guess we have to decide if it is worth it. I have been running Virtual Box with an XP install for the last year or so to get around issues like these. Works well if your hardware is up to it.

Linux/Window... different tools for different jobs. But it is frustrating the way the most popular OSs are going with Ubuntu and Unity and Windows with the tiles. I know there are ways around these but...

[Chirpy]

yea, the tiles is what bugs me most. I think I rather just finish up my gedit mods and use that, pretty much every other programming language uses gEdit also in linux, so I might as well just add it in and get it working. makes it easier to do everything up in anyways. I always used gedit to mess with python stuff rather than IDLE because it starts faster and does the same thing more or less, also I end up usually just starting the programs from the command line with python. so gedit works better for me with that.

also, Ive never used pbp3 because of the new keywords and such, also most of the code out there is still using pbp 2 for everything, so I just stick with my 2.6 version that I have. I know that the old code probably should work with the 3.x but why upgrade when you already have something that works good :P

atm, as far as I can tell, everything works in gedit for compiling, code highlighting, and all of those features. The compiling and burning using pickit2 works too, Ive used it a few times to upload code to my robot. The only thing that isnt implemented yet is a chip selector, but anyone who programs stuff in linux and have gotten this far should probably be able to get back into external tool's manager, and just change the chip name there, where they added in the scripts. nothing too hard and it is changable, and quite easy at that imo.

I know the scripts are in the ~/.gnome2/gedit/tools/ so it shouldn't be too hard to just write a program to be called up and modify that value in the code in those scripts.

little by little, it'll get finished

[Chirpy]

ok, went through and fine tuned everything with pickit2 part, just change it to this and it should work perfectly.

#!/bin/sh
pic="16f628a"
wine c:/pbp/pbpw -e -s -ac:/Program Files/Microchip/MPASM Suite/MPASMWIN -p$pic $GEDIT_CURRENT_DOCUMENT_NAME
var=$GEDIT_CURRENT_DOCUMENT_NAME
var2=${var%???}
outasm=$var2"ASM"
wine c:/Program\ Files/Microchip/MPASM\ Suite/mpasmwin /q /e /l $outasm
outhex=${var2}"HEX"
pk2cmd -B/usr/share/pk2/ -PPIC$pic -F$outhex -M -R

I just wrote some code to my robot a few mins using this and the pickit2, so I know it works fine now. found out I needed to include the device file path and PIC to -PPIC$pic part.

here's the updated JDM part too:

#!/bin/sh
comport="/dev/ttyS0"
pic="16f628a"
wine c:/pbp/pbpw -e -s -ac:/Program Files/Microchip/MPASM Suite/MPASMWIN -p$pic $GEDIT_CURRENT_DOCUMENT_NAME
var=$GEDIT_CURRENT_DOCUMENT_NAME
var2=${var%???}
outasm=$var2"ASM"
wine c:/Program\ Files/Microchip/MPASM\ Suite/mpasmwin /q /e /l $outasm
outhex=${var2}"HEX"
picprog --erase --burn --input $outhex --device pic$pic --p $comport

also, here's the new and easier version of compile pbp code command.

#!/bin/sh
pic="16f628a"
wine c:/pbp/pbpw -e -s -ac:/Program Files/Microchip/MPASM Suite/MPASMWIN -p$pic $GEDIT_CURRENT_DOCUMENT_NAME
var=$GEDIT_CURRENT_DOCUMENT_NAME
var2=${var%???}
outasm=$var2"ASM"
wine c:/Program\ Files/Microchip/MPASM\ Suite/mpasmwin /q /e /l $outasm

in both of these, just change the 16f628a in the quotation marks at the top to change the chip, it's as simple as that now.
sorry about the mixup, had to reinstall linux on here a few days ago, so had to work out all of the little bugs