Enlightenment CVS committal

Author  : andreas
Project : e17
Module  : proto/eflpp

Dir     : e17/proto/eflpp


Modified Files:
        README 
Added Files:
        eflpp.anjuta 
Removed Files:
        eflpp.prj 


Log Message:
- some temporary debug messages in Esmart
- README updated
- replaced Anjuta 1 with Anjuta 2 files (Hint: Anjuta isn't needed for 
building; only optional project support)

===================================================================
RCS file: /cvs/e/e17/proto/eflpp/README,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -3 -r1.1 -r1.2
--- README      3 Jul 2007 22:42:22 -0000       1.1
+++ README      8 Aug 2007 19:32:03 -0000       1.2
@@ -11,16 +11,12 @@
 A: LGPL
 
 Q: What are the requirements?
-A: You need a C++ toolchain (recommended: g++ 4.1.1), qmake 2.00a (from Qt4), 
libsigc-2.x, Evas, Ecore, Edje.
+A: You need a C++ toolchain (recommended: g++ 4.1.1), libsigc-2.x, Evas, 
Ecore, Edje.
    For a debugging build, you need libcwd, see http://libcwd.sourceforge.net
-   Optional parts need Esmart, Epsilon, Ewl, Etk, and Emotion - you can 
configure the build by modifying include.pro
+   Optional parts need Esmart, Epsilon, Ewl, Etk, and Emotion
 
-Q: How do I build efl++?
-A: source makevars.sh; qmake efl++.pro; make
-
-Q: What's that qmake thing? Where is the autotools stuff or the handcrafted 
Makefile?
-A: I'm not very fond of autoconf and friends, nor do I like handcrafted 
Makefiles.
-   qmake is a build utility done by TrollTech - see 
http://doc.trolltech.com/4.0/qmake-manual.html
+Q: How do I build eflpp?
+A: ./autogen.sh && make && make install
 
 Q: Why no inline functions [yet]?
 A: Premature optimization is the root of all evil.
@@ -30,8 +26,8 @@
    After all, I'm targetting embedded systems...
 
 Q: Why a monolithic library and not just one library for every EFL sublibrary?
-A: EFL++ as a class library benefits from putting everything into one library.
-   I may reconsider this when I have more knowledge about the EFL++ use-cases.
+A: EFLpp as a class library benefits from putting everything into one library.
+   I may reconsider this when I have more knowledge about the EFLpp use-cases.
 
 Q: How stable is the API yet?
 A: Not at all! Trust me, everything can change. I know this is a bit sucky for 
all potential



-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
enlightenment-cvs mailing list
enlightenment-cvs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-cvs

Reply via email to