| PortingToBeOS |
 |
BeBits > TableOfContents > DeveloperArea
You've decided to port an app to BeOS. Good for you. Here are some tips on porting.
- Make sure someone hasn't already ported it. (yeah I know it's some obscure software....)
- Check bebits.
- Check GeekGadgets, especially for unix-type command line apps.
- Check Google.
- Look in the archives for a mailing list for development for the particular app.
- Look on BeShare.
- Make sure you are using an appropriate compiler/tools for your program.
- Read the website for your app to find out what tools and versions you will need.
- Download tools from the web site for the particular app.
- Download tools on BeShare.
- Download tools from BeBits' Development Section.
- Download the up-to-date and stable compiler gnupro-000224-bin.tgz from geekgadgets.
- -or- If using MMX or other processor enhancements, download the not-quite-so-stable-but-has-MMX build from here on bebits.
- Make sure you have all the libraries that you need.
- Read the website for your app to find out what libraries and versions you will need.
- Download libraries from the web site for the particular app.
- Download the library binary from the web site for the library. (web site is usually more up to date than bebits)
- -also- Check BeShare for libraries.
- -also- Check BeBits' Development Section for libraries. Some useful libraries follow:
- libdl.so - a library for dynamic linking. if your app has -ldl in the compilation, you can try this lib.
- Download the sources for the library, and it's time to port the library! Start over at step 1. :-)
- Try to build it! Usually for most apps the process goes something like this:
- ./configure --prefix=/boot/home/config
- make
- make install
- It didn't build... put those programming skills to work.
- Check out these possible ProblemsBuildingSharedLibraries.
- Talk to people on BeShare.
- Talk to the original developers.
- Look for help on Google Groups or the newsgroups.
- It built!
- Test the application
- Give feedback to the application's original authors.
- Include diffs required for the port. Try not to break anything. :-)
- Notify them of any issues. (perhaps part did not build, for example)
- Write up a small description of how you built it
- Package it for other users
- Post it to bebits!
|
|
|
