the editor for Fiasco.OC
Björn Döbel
doebel at os.inf.tu-dresden.de
Thu Mar 19 09:41:03 CET 2015
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
To directly answer your question: most people here use either vim or
emacs.
In general, you can work on Fiasco code with any editor you want.
There are two things you need to be aware of:
1. As this is a non-standard project, you will have to configure your
editor to find the proper header files for code completion. There
are a couple of examples on how to setup this for L4Re here:
http://wiki.tudos.org/IDE_Setup -- you will have to adapt this for
Fiasco.
2. Fiasco uses a preprocessing step, that is the source code contains
non-C++ features (such as the EXTENSION thing in your example)
and that will let some parsers choke. To understand what the
preprocessor does and what these non-standard features mean, please
check the preprocess documentation in l4/tool/preprocess.
Bjoern
On 19.03.2015 03:27, cui.yunfeng at zte.com.cn wrote:
>
> I am reading Fiasco.OC source code, but didn't find a suitable
> editor. As the following code, the eclipse or Source Insight can't
> identify the class hierarchy. I want to know which editor is used
> by Fiasco.OC developer, Thanks !
>
> class Kernel_uart { public:
>
> };
>
> ....
>
> EXTENSION class Kernel_uart : public Uart { private:
>
> };
>
>
> _______________________________________________ l4-hackers mailing
> list l4-hackers at os.inf.tu-dresden.de
> http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
>
- --
Dr.-Ing. Bjoern Doebel Mail: doebel at tudos.org
TU Dresden, OS Chair Phone: +49 351 463 38 799
Noethnitzer Str. 46 Fax: +49 351 463 38 284
01187 Dresden, Germany WWW: http://www.tudos.org/~doebel
- --
"When the seagulls follow the trawler, it's because they think
sardines will be thrown into the sea." (Eric Cantona)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iEYEARECAAYFAlUKi5sACgkQP5ijxgQLUNlYKwCgk9WP+wMaWTbnFtQRZQe+IVj+
ywMAoIGj64jR/2rzz8BqBJgYvEVYoZj1
=NMzO
-----END PGP SIGNATURE-----
More information about the l4-hackers
mailing list