Re: [Wengophone-devel] SVN et Compilation

[Philippe BERNERY]

[EMAIL PROTECTED] a écrit :

Hi Philippe,

I ever try on the 13114 revision, it's my current working revision ...

I saw on the Wengo website that the new version of openwengo, the NG 
version, was working with MinGW compilation instead of VisualC++ no ?


Compilation works if I remember well but execution is not stable. And we 
don't have enough resources to work on MinGW support. Feel free to make 
it work :-).


--
Philippe Bernery
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] Logging committed

[Andreas Schneider]

Aurélien Gâteau wrote:
> I just committed my logging changes, as well as support for OWLOGGER_DEFAULT 
> environment variable. I also documented the usage of the environment 
> variables in a new file named DEBUGGING.txt.

Great work, thanks!

-- andreas

> 
> Aurélien
> ___
> Wengophone-devel mailing list
> Wengophone-devel@lists.openwengo.com
> http://dev.openwengo.com/mailman/listinfo/wengophone-devel
> 

-- 
http://www.cynapses.org/ - cybernetic synapses




signature.asc
Description: OpenPGP digital signature
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] SVN et Compilation

[wengophone-devel]

Hi Philippe,

I ever try on the 13114 revision, it's my current working revision ...

I saw on the Wengo website that the new version of openwengo, the NG 
version, was working with MinGW compilation instead of VisualC++ no ?


I'm going to try with the VisualC++ express ...

Thanks
Yves

Philippe BERNERY a écrit :

[EMAIL PROTECTED] a écrit :

Hi Yves,

This list is in English to give access to the project to more people. 
I answer in English.


Welcome aboard.
> Tout d'abord, j'ai passé plusieurs heures pour rérupérer la version 2.1
> via SVN, ne peut-on télécharger la 1ère fois un seul fichier complet
> tar.gz ? Un téléchargement complet via SVN n'est pas chose facile,
> enfin, longue ...

A source package is created for each release version of WengoPhone but 
there is no source package for SVN version.


> Voici ce que j'ai lors de l'exécution de la commande :
> cmake -DCMAKE_BUILD_TYPE=Debug -G "MinGW Makefiles" ..
>

MinGW compilation does not completely with WengoPhone. You should 
better use Visual C++ Express 2005 or Visual C++ 2003.


> -- Time: 20071012160536
> CMake Error: Please install the Boost libraries and development 
packages


Can you try with revision 13114? I did have the same problem on my 
machine.


--
Philippe Bernery
http://dev.openwengo.org



___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] Help of building with boost configuration error

[Philippe BERNERY]

Hi,


So I don't know why it always report the boost configuration problem.
Could anybody give me some help? Thanks very much!


Can you try rev. 13114? It may fix your problem.

--
Philippe Bernery
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] SVN et Compilation

[Philippe BERNERY]

[EMAIL PROTECTED] a écrit :

Hi Yves,

This list is in English to give access to the project to more people. I 
answer in English.


Welcome aboard.
> Tout d'abord, j'ai passé plusieurs heures pour rérupérer la version 2.1
> via SVN, ne peut-on télécharger la 1ère fois un seul fichier complet
> tar.gz ? Un téléchargement complet via SVN n'est pas chose facile,
> enfin, longue ...

A source package is created for each release version of WengoPhone but 
there is no source package for SVN version.


> Voici ce que j'ai lors de l'exécution de la commande :
> cmake -DCMAKE_BUILD_TYPE=Debug -G "MinGW Makefiles" ..
>

MinGW compilation does not completely with WengoPhone. You should better 
use Visual C++ Express 2005 or Visual C++ 2003.


> -- Time: 20071012160536
> CMake Error: Please install the Boost libraries and development packages

Can you try with revision 13114? I did have the same problem on my machine.

--
Philippe Bernery
http://dev.openwengo.org


___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

[Wengophone-devel] Logging committed

[Aurélien Gâteau]

I just committed my logging changes, as well as support for OWLOGGER_DEFAULT 
environment variable. I also documented the usage of the environment 
variables in a new file named DEBUGGING.txt.

Aurélien
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] Logging

[Aurélien Gâteau]

On Thursday 18 October 2007 16:00:52 Dave Neary wrote:
> Hi,
>
> Aurélien Gâteau wrote:
> > Attached patches implement this. It would be nice to have your opinion on
> > them. Note that it will cause a big recompile, since it changes Logger.h
> > :-/
> >
> > One thing I would like to add is support for a OWLOGGER_DEFAULT
> > environment variable, which would define the default minimum level for
> > all logger components. This would make it easier to get a full log output
> > from a user: only need to ask him to set OWLOGGER_DEFAULT to 0, reproduce
> > the bug, then post the big log file. Then we can filter the output
> > ourself.
> >
> > What do you think about this?
>
> Sounds goot to me as-is. we will need this documented, of course
> (slightly better than it's done in SANE, please ;)

Ok will commit then. And write some doc.
Prepare for a long recompile :-)

Aurélien
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] Logging

[Dave Neary]

Hi,

Aurélien Gâteau wrote:
> Attached patches implement this. It would be nice to have your opinion on 
> them. Note that it will cause a big recompile, since it changes Logger.h :-/
> 
> One thing I would like to add is support for a OWLOGGER_DEFAULT environment 
> variable, which would define the default minimum level for all logger 
> components. This would make it easier to get a full log output from a user: 
> only need to ask him to set OWLOGGER_DEFAULT to 0, reproduce the bug, then 
> post the big log file. Then we can filter the output ourself.
> 
> What do you think about this?

Sounds goot to me as-is. we will need this documented, of course
(slightly better than it's done in SANE, please ;)

Cheers,
Dave.

-- 
Dave Neary
OpenWengo Community Development Manager
Email: [EMAIL PROTECTED]
Tel: +33 9 51 13 46 45
Mob: +33 6 28 09 73 11
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] Logging

[Aurélien Gâteau]

On Monday 15 October 2007 15:57:40 Alec leamas wrote:
> First of all. logging is important, a primary tool to find out
> and handle problems. It's worth some time.
>
> Secondly, I think we need to implement the specified ways to
> limit and route the output.

Agreed.

> And, this is the complicated thing: I think we need to
> implement some kind of "log source" semantics, and make it
> possible to say things like "I want all error and warning
> messages, and also the debug messages from
> osip". This means semantics similar to log4j or syslog. This
> is code enough to try to find a reasonable logging package,
> there are some out there (log4c?)

I am a bit reluctant to change to a new logging system at this point of the 
2.2 development.

I just made a simple change to the existing Logger class to make it possible 
to categorize logs and to be able to change the minimum log level through 
environment variables. It's a bit inspired  from the internal logging 
system of SANE, which I found quite good.

Here is how it works: By default all log output belongs to the "Common" 
logger. If you want to define a new log component, you define 
OWLOGGER_COMPONENT to something else before including Logger.h. Like this:

#define OWLOGGER_COMPONENT "MyComponent"
#include 

By default only messages with Info level or higher will be output. You can 
change this at runtime by defining an environment variable:

export OWLOGGER_MYCOMPONENT=0

This will output messages from all levels, since 0 is the lowest log level.
- 0 => Debug
- 1 => Info
- 2 => Warn
- 3 => Error

Attached patches implement this. It would be nice to have your opinion on 
them. Note that it will cause a big recompile, since it changes Logger.h :-/

One thing I would like to add is support for a OWLOGGER_DEFAULT environment 
variable, which would define the default minimum level for all logger 
components. This would make it easier to get a full log output from a user: 
only need to ask him to set OWLOGGER_DEFAULT to 0, reproduce the bug, then 
post the big log file. Then we can filter the output ourself.

What do you think about this?

Aurélien
Index: libs/owutil/util/src/File.cpp
===
Index: libs/owutil/util/src/Logger.cpp
===
--- libs/owutil/util/src/Logger.cpp	(révision 13107)
+++ libs/owutil/util/src/Logger.cpp	(copie de travail)
@@ -22,6 +22,7 @@
 #include 
 #include 
 #include 
+#include 
 
 #include 
 #include 
@@ -29,6 +30,8 @@
 #include 
 #include 
 
+static const char* OWLOGGER_PREFIX = "OWLOGGER_";
+
 Logger* Logger::getInstance() {
 	static Logger instance;
 	return &instance;
@@ -56,33 +59,65 @@
 	return _logFileName;
 }
 
-void Logger::debug(const std::string & className, const std::string & message) {
-	log(Debug, className, message);
+void Logger::debug(const std::string & component, const std::string & className, const std::string & message) {
+	log(component, Debug, className, message);
 }
 
-void Logger::info(const std::string & className, const std::string & message) {
-	log(Info, className, message);
+void Logger::info(const std::string & component, const std::string & className, const std::string & message) {
+	log(component, Info, className, message);
 }
 
-void Logger::warn(const std::string & className, const std::string & message) {
-	log(Warn, className, message);
+void Logger::warn(const std::string & component, const std::string & className, const std::string & message) {
+	log(component, Warn, className, message);
 }
 
-void Logger::error(const std::string & className, const std::string & message) {
-	log(Error, className, message);
+void Logger::error(const std::string & component, const std::string & className, const std::string & message) {
+	log(component, Error, className, message);
 }
 
-void Logger::fatal(const std::string & className, const std::string & message, const std::string & filename, const std::string & line) {
-	log(Fatal, className, message, filename, line);
+void Logger::fatal(const std::string & component, const std::string & className, const std::string & message, const std::string & filename, const std::string & line) {
+	log(component, Fatal, className, message, filename, line);
 	flush();
 	assert(NULL && "fatal error");
 }
 
-void Logger::log(Level level, const std::string & className, const std::string & message, const std::string & filename, const std::string & line) {
+static Logger::Level minLevelForComponent(const std::string & component) {
+	static std::map levelMap;
+	std::map::const_iterator it = levelMap.find(component);
+
+	if (it == levelMap.end()) {
+		std::string envName = OWLOGGER_PREFIX + String(component).toUpperCase();
+		char* ptr = getenv(envName.c_str());
+		if (!ptr) {
+			levelMap[component] = Logger::Info;
+			return Logger::Info;
+		}
+
+		String strValue(ptr);
+		int value = strValue.toInteger();
+		Logger::Level level;
+		if (value > int(Logger::Fata

[Wengophone-devel] Re: [Wengophone-commit] r13085 - owutil/branches/wengophone-2.2/system/src/unix

[Aurélien Gâteau]

On Wednesday 17 October 2007 14:23:36 [EMAIL PROTECTED] wrote:
> Log:
> OK, no popen() ;-). Don't leak a file descriptor...

Hehe, good catch!

Aurélien
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] New in this!!

[Andreas Schneider]

Joel Silva wrote:
> Thanks for the quick reply!;)
> I read the link you you sent but I don't know what modifications I'm
> supposed to do...
> For a newbie like me its a little hard to understand what I should do
> looking only for that site.

You need to run cmake which creates the MSVC files. For more information see
http://www.cmake.org/

I'm not a Windoze user so someone else has to help you from that point. Feel
free to improve the documentation on the trac wiki.

-- andreas

> 
> Br,
> 
> Joel Silva
> 
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Andreas Schneider
> Sent: quinta-feira, 18 de Outubro de 2007 12:34
> To: wengophone-devel@lists.openwengo.com
> Subject: Re: [Wengophone-devel] New in this!!
> 
> Joel Silva wrote:
>> Hello all.
>> I was looking to get a look at the openwengo but I can't understand 
>> what steps I have to do to put this working on the VS2003.
>> I install the Visual SVN plugin and created a new solution.
>> I have downloaded the source code through the Visual SVN to the 
>> Solution but now I don't know what to do... Do I have to create a new
> Project?
>> Please guide me through the steps that I have to do.
> 
> Hi,
> 
> take a look at
> 
> http://dev.openwengo.org/trac/openwengo/trac.fcgi/wiki/HowToBuildFromSou
> rce
> 
>>  
>> BR,
>>
>> *Joel Silva**
>> *Analyst
>>
> 
> Cheers,
> 
>   -- andreas
> 
> 

-- 
http://www.cynapses.org/ - cybernetic synapses




signature.asc
Description: OpenPGP digital signature
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

[Wengophone-devel] Builder for 2.1 down?

[Dave Neary]

Hi,

I just noticed that the 2.1 nightly builds for Linux stopped at r13085 -
  we're up to r13107 as of 9pm yesterday, and 13085 dates from 14:23
yesterday.

Is the builder for the 2.1 branch activated in the buildbot?

Cheers,
Dave.

-- 
Dave Neary
OpenWengo Community Development Manager
Email: [EMAIL PROTECTED]
Tel: +33 9 51 13 46 45
Mob: +33 6 28 09 73 11
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Re: [Wengophone-devel] New in this!!

[Andreas Schneider]

Joel Silva wrote:
> Hello all.
> I was looking to get a look at the openwengo but I can't understand what
> steps I have to do to put this working on the VS2003.
> I install the Visual SVN plugin and created a new solution.
> I have downloaded the source code through the Visual SVN to the Solution
> but now I don't know what to do... Do I have to create a new Project?
> Please guide me through the steps that I have to do.

Hi,

take a look at

http://dev.openwengo.org/trac/openwengo/trac.fcgi/wiki/HowToBuildFromSource

>  
> BR,
> 
> *Joel Silva**
> *Analyst
> 

Cheers,

-- andreas



signature.asc
Description: OpenPGP digital signature
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

[Wengophone-devel] New in this!!

[Joel Silva]

Hello all.
I was looking to get a look at the openwengo but I can't understand what
steps I have to do to put this working on the VS2003.
I install the Visual SVN plugin and created a new solution.
I have downloaded the source code through the Visual SVN to the Solution
but now I don't know what to do... Do I have to create a new Project?
Please guide me through the steps that I have to do.
 
BR,

Joel Silva
Analyst


.

Novabase
Av. Eng. Duarte Pacheco, 15F . 1099-078 Lisboa - Portugal
Tel. (+351) 213 836 300 . Fax (+351) 213 836 301 .
mailto:[EMAIL PROTECTED]  
www.novabase.pt  

 
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel