Meta tags:
keywords= linux palm palmOS development prc-tools;
Headings (most frequently used words):
get, palmos, linux, development, tips, and, problems, to, be, aware, of, first, prc, tools, next, pilrc, sdk, compiling, program, some, links,
Text of the page (most frequently used words):
the (59), you (46), and (38), palm (28), tools (22), with (22), sdk (21), that (19), for (18), prc (17), which (17), have (15), linux (15), this (15), they (14), can (13), some (12), get (11), work (9), from (9), versions (9), code (9), your (8), don (8), #palmos (8), working (8), one (8), more (8), include (8), rpm (8), palmdev (8), not (7), make (7), page (7), need (7), sdks (7), development (7), just (7), pilrc (7), opt (7), are (6), but (6), program (6), pilot (6), also (6), sample (6), all (6), tarball (6), like (5), directory (5), includes (5), out (5), their (5), about (5), them (5), find (5), files (5), any (5), version (5), may (5), what (4), well (4), developers (4), then (4), will (4), look (4), links (4), documentation (4), compile (4), link (4), older (4), sdk_version (4), probably (4), into (4), there (4), things (4), tell (4), first (4), want (4), pick (4), fine (4), got (3), after (3), time (3), setting (3), gcc (3), use (3), project (3), now (3), apis (3), between (3), other (3), haven (3), cyberport (3), faq (3), pose (3), only (3), programmer (3), software (3), site (3), download (3), where (3), rom (3), did (3), far (3), later (3), run (3), once (3), never (3), again (3), lot (3), set (3), works (3), newer (3), support (3), earlier (3), environment (3), apps (3), than (3), end (3), comes (3), install (3), libraries (3), these (3), here (2), instructions (2), idea (2), already (2), might (2), too (2), much (2), together (2), called (2), sdkfind (2), ifdefs (2), told (2), going (2), away (2), through (2), info (2), book (2), unix (2), mailing (2), very (2), programming (2), floating (2), point (2), xpilot (2), how (2), found (2), howto (2), official (2), information (2), getting (2), developer (2), under (2), tutorial (2), new (2), been (2), try (2), list (2), sure (2), running (2), readme (2), getrom (2), know (2), though (2), faster (2), when (2), fltk (2), seems (2), used (2), case (2), different (2), something (2), pre (2), prctools (2), collaborating (2), fill (2), changed (2), turns (2), who (2), still (2), using (2), old (2), break (2), why (2), shouldn (2), problems (2), own (2), both (2), gdbpanel (2), directories (2), come (2), codewarrior (2), extract (2), installed (2), usr (2), local (2), should (2), two (2), lib (2), gives (2), few (2), names (2), mac (2), form (2), worked (2), sourceforge (2), describe (2), chances, web, search, spending, beating, head, against, wall, trying, follow, based, thinking, would, develop, stuff, whether, supports, device, way, wasted, finally, setup, putting, help, fellow, makefile, compiler, calls, appropriate, call, differ, continue, mechanisms, akkana, shallow, sky, home, general, saw, recommended, programmers, lists, reilly, weak, recommend, seen, myself, bible, doug, sparling, note, yet, does, emulator, api, html, acrobat, yay, companion, palmgear, making, connection, lots, useful, elsewhere, started, including, release, coming, afraid, cautious, posting, read, stay, topic, forcibly, unsubscribed, skins, tells, image, debug, images, somehow, registering, secret, handshake, learned, excellent, assume, gotten, immediately, patient, took, hour, over, serial, line, 9600, baud, could, backup, copies, had, trouble, xcopilot, manage, emulatorsrc_3, unfortunately, stopped, upgraded, agenda, toolchain, managed, back, change, alas, emulators, whichever, being, machine, cflags, dsdk_, defined, sdk_31, else, endif, better, approach, ever, share, anyone, plenty, built, quick, fix, remove, lines, newfloatmgr, scrdrivernew, replace, differences, functionality, advanced, color, supposedly, iiixe, see, cause, crashes, machines, visor, deluxe, equally, right, yourself, either, agree, handle, true, many, people, especially, leery, upgrading, lazy, forms, upgrade, rewrite, projects, stick, whatever, blame, newest, tips, aware, start, samples, planetary, simulation, compiles, binary, xlib, interested, environments, test, algorithms, each, marsmap, astro, errorcodes, multiapp, folks, gausstest, syslib, those, type, uses, pay, attention, even, makefiles, beginning, hassle, worth, instead, downloaded, compiling, let, flip, coin, default, various, suggests, symlink, rely, number, correct, place, backward, compatibility, having, subdirectories, sparse, ways, extracted, useless, plus, throw, rest, save, day, second, contains, same, extracts, incs, love, long, spaces, think, paths, copied, latter, three, single, further, hassles, advice, telling, below, easy, enough, sign, times, everything, bit, harder, open, source, current, writing, supported, tar, file, containing, header, hit, weird, checked, redhat, ended, 5b7, previously, 1mdk, i586, rpmfind, next, programs, while, happens, alive, latest, builds, i386, forget, hopeless, doesn, doing, great, disservice, keeping, recently, has, updated, helpful, article, modern, easier, developing, arm, architectures, definitely, howtos, won,
Text of the page (random words):
linux palmos development linux palmos development chances are you got here after a web search after spending some time beating your head against the wall trying to follow palm s instructions on setting up the gcc based prc tools they don t work do they what is palm thinking i have no idea but some of us would like to develop palmos stuff on linux whether or not palm supports the idea we ve got the device already might as well make use of it and after way too much time wasted i finally got a working setup so i m putting together this page to help fellow linux developers more recently the prc tools sourceforge page has been updated and includes information about how to install from rpm it may be helpful as may this article on setting up the prc tools in linux both of these are more modern than my howto and describe newer versions of the tools which may or may not make things easier if you re developing for arm architectures then you definitely need the newer howtos the versions i describe here won t work first forget about the prc tools link palm gives you it s hopeless doesn t work at all as far as i can tell palm is doing a great disservice to linux developers by keeping that link on their site first get prc tools as it happens the prc tools project is alive and well and the latest builds work fine with any sdk go get it from the sourceforge page i installed the rpm prc tools 2 0 92 1 i386 rpm which worked fine pick up the tarball of sample programs while you re there next get pilrc i haven t hit any weird version problems with pilrc i just checked it for install in my redhat 7 1 and ended up with pilrc 2 5b7 4 seems to work previously i used pilrc 2 7b 1mdk i586 rpm which also worked fine probably any pilrc you can find at rpmfind should be fine get a palmos sdk this is a bit harder you do need to get that from palm it s not open source the current version as of this writing is sdk 4 0 and sdk 3 5 is still supported on palm s site there s also a tar file containing sdks 1 2 and 3 1 no libraries just header files it turns out you don t need libraries for these earlier sdks my advice is to get them all if you end up collaborating with other palm developers there s no telling what version they will have more on that below and it s easy enough to sign palm s form a few more times and just pick up everything the documentation that comes with the sdks is sparse 4 0 comes two ways first a tarball which when extracted gives you a few useless directories plus an rpm you can install the rpm and throw the rest away save the tarball you may need to do this again some day second a different tarball which contains the same files again which extracts into palm os support incs and palm os support gcc libraries palm is just in love with long directory names with spaces in them i think these are the mac codewarrior paths which then have to be copied into opt palmdev sdk 4 include lib 3 5 comes only in the latter form i e the mac directory names the older three sdk versions come together in a single tarball which you can extract in opt palmdev with no further hassles with any sdk what you want to end up with is a directory called opt palmdev sdk xx where xx is the version number e g 2 4 3 5 some tools look in opt palmdev some look in usr local palmdev but i m told that opt is the correct place and usr local is only for backward compatibility the palmdev sdk x directory should end up having two subdirectories include and lib now pick one sdk probably 4 0 or 3 5 flip a coin and make it the default if you list the files in the rpm rpm ql prc tools you ll find that it installed various documentation files one of them is a readme and one of the things it suggests is to make a symlink from opt palmdev sdk version to opt palmdev sdk do this if you want sample apps to compile you probably shouldn t rely on this in your own code though i ll tell you why later now you have a working palm development environment let s compile some code compiling a program don t pay any attention to the sample apps that come with the sdk they re set up for codewarrior or something and don t even have makefiles so for a beginning linux palm programmer they re more hassle than they re worth instead extract that prc tools sample tarball you downloaded earlier as of 2 0 92 i find that errorcodes and multiapp don t compile i ll work that out with the prc tools folks but gausstest gdbpanel and syslib do so cd into one of those directories and type make gdbpanel uses pilrc so try that one if you want to make sure you have a working pilrc as well as prc tools or if you don t like the prc tools samples you can look at my palm astro software page or my marsmap page where i have code for some planetary simulation apps some of which also compiles to a linux binary using xlib in case you re interested in sample code that works in both environments i find it a lot faster to test algorithms on linux than to download a new prc to the palm each time if this works your development environment is working and you can start working on your own code tips and problems to be aware of why did you tell me to pick up old sdk versions shouldn t i program with the newest one first it turns out that many people who are still programming with the prctools especially on linux are using very old sdks 3 1 or earlier they re leery that upgrading might break things or they re just lazy and don t want to go fill out more of palm s forms they also know that palm changed all the include files for sdk 3 5 and if they upgrade all their includes will break and they ll have to rewrite their projects so they just stick with whatever working environment they have who can blame them if you find yourself collaborating with other developers you either need to agree on an sdk or fill your code with ifdefs which handle all the includes and apis which changed between versions this is true from 3 5 to 4 0 too not just from pre 3 5 to 3 5 there are also some differences in functionality 4 0 can do some things that 3 5 can t like more advanced color support supposedly i have a iiixe so i ll never see that some of the 4 0 apis cause crashes on machines running older versions of the os like the visor deluxe as far as i can tell 3 5 and 4 0 work equally well with linux prctools once you use the right includes you ll probably run into plenty of sample code built for pre 3 5 sdks a quick fix to get older code to run on newer sdks is to remove the lines for pilot h newfloatmgr h and scrdrivernew h and replace them all with an include of palmos h a better approach in case you ever need to share code with anyone on a different sdk is something like this if defined sdk_31 include include include else sdk 3 5 and later include endif sdk versions then in your project s makefile do this set sdk_version to whichever sdk is being used on this machine sdk_version 3 5 cflags palmos sdk_version dsdk_ sdk_version 1 now the compiler which calls a program called sdkfind will look in the appropriate directory and you can do ifdefs in your program if you need to call apis which differ between sdks i m told sdkfind is going away but palmos will continue to work in prc tools through other mechanisms q what about emulators a i ve had a lot of trouble getting older versions of pose xpilot and xcopilot to work but i did once manage to get emulatorsrc_3 3 working unfortunately it stopped working when i upgraded fltk for the agenda toolchain and i ve never managed to go back to a set of tools under which pose works fltk seems to change a lot between versions alas if you do get it running you ll have to download skins for it the readme tells you where and you ll have to get a rom image you can get debug rom images from palm somehow registering for their developer program which i did then going through a secret handshake which i haven t learned or you can use pi getrom from the excellent pilot link tools i assume you already know about pilot link if you ve gotten this far if not download it immediately be patient pi getrom took about an hour for me over a serial line at 9600 baud though later i found i could run much faster make backup copies of your rom once you have it so you ll never have to do that again some links the prc tools project they have a new release coming out but i ve been afraid to try it be cautious posting to their mailing list be sure to read the faq and stay on topic or you ll be forcibly unsubscribed palm s official page on development tools including linux info prc tools tutorial tutorial for sdk 3 5 and gcc cyberport s palmos programmer faq setting up developer tools for pilot under unix getting started with prc tools from cyberport lots more useful information elsewhere on that site palm pilot software development with linux palm and linux making the connection palmgear s software development links palm os programmer s companion official api documentation in html not acrobat yay palm os emulator howto note this is for pose not xpilot it also includes instructions on how to compile a program for the palm the only page i ve found yet which does cyberport floating point faq palm s documentation on floating point doug sparling s links palm os programming bible a book i saw recommended by unix programmers on one of the mailing lists the o reilly book is very weak and i don t recommend it i haven t seen this one myself general palm pilot links linux info shallow sky home akkana
|
