new compilers and languages support

[MariuszP]

I was wandering if it is possible and how much work would it take to add support for new compilers and languages. For example I would gladly see CB supporting development of apps for Pocket PC or Palm. As for languages I'm interested in adding support for Lua syntax and compiler (interpreter).

Any clues how to accomplish such task?

[Michael]

Any clues how to accomplish such task?

You can look as example the wiki topic "Installing Fortran Compiler" (http://wiki.codeblocks.org/index.php?title=Installing_Fortran_Compiler). Moreover, C::B supports the SDCC compiler (http://sdcc.sourceforge.net/).

Michael

[MariuszP]

I'll take a look at rhe fortran installation guide.
As for SDCC, how large subset of current ipaq's , palms uses processors mentioned in sdcc support list? Anyone knows? I may be wrong but new versions are based on completely different processors. So I'm wondering if sdcc will be able to compile apps for this new processors.

I'm trying to start ipaq development, I'm completely new to this so my questions might be stupid

[Michael]

Hello,

I am not sure that SDCC can be used to develop applications for ipaq (I have checked a bit on the website, but I did not find anything). You can try to post a question to the SDCC forum.

May be this could be interesting for you:

http://www.pocketgear.com/software_detail.asp?id=5723&associateid=9
But it is relatively old.

http://packages.qa.debian.org/p/pocketpc-gcc.html
Even if it is from Debian, I have read that it can work for win32 (http://www.digitalmars.com/d/archives/D/gnu/1247.html)
May be this could be implemented within C::B.

This link could also be useful:

http://www.codeproject.com/ce/Pocket_PC_Development.asp

You can also try to google to get more info.

Michael

[MariuszP]

I'v took a look at thoose sites. It looks promising, but I't still WIP as far as I understood. Anyway, I will keep looking. I'll give some info when I'll find something usefull...

[Michael]

I'v took a look at thoose sites. It looks promising, but I't still WIP as far as I understood. Anyway, I will keep looking. I'll give some info when I'll find something usefull...

I have found or old stuff or as you said WIP, at least for C/C++. May be other languages, e.g., Java ( :roll:) might have something more updated and/or stable.

Michael

[Michael]

Hello,

An interesting possibility for PocketPC development could be to import into C::B the compiler, linker and resource compiler of Pelles C.

Until now, only ARM processors (including XScale) are supported.

Michael

[MariuszP]

It is really nice stuff. I'v took a quick looka at it and it looks promising. But it is c compiler, and I was hoping to do some wxWidgets dev for pocket PC. And wx is c++ lib. But it would be really nice to integrate it with CB.
I'll try to investigate this in my spare time....
Thx Michael...

[Michael]

Hello,

It seems rather difficult to find a free c++ for Pocket PC. wxWinCE seems to require Embedded Visual Tools 3 or 4 which are not free (for what I know). Moreover, I have seen an article on how convert a Embedded Visual Tools 3 or 4 project to Visual Studio 2005. May be M$ is trying to make Pocket PC developers move to Visual Studio 2005. Unfortunately, it seems that Visual Studio Express is not suitable for that ( :roll:).

May be you can give a try to Pocket GCC. The project seems to be dead , but they speak about a Yahoo Group. May be you can check there.

Michael

PS.: Intel C++ compiler seems now to support Pocket PC development, but it is not free and you have to buy a license .

[MariuszP]

Yes, M$ is integrating everything in VS 2005. I'v seen it' I'v played with it and it's really nice product. I'm using this in job, but in home i prefer CB, so I Was hoping that I will be able to find something that I could use. Eventually I'll check VS embedded once again.
And of course I will check PocketGCC.

Thx again Michael.

[Michael]

Eventually I'll check VS embedded once again.

May be it would be possible to use the compiler, linker, etc. of VS embedded in C::B. That would be not so bad .

Michael