Re: [Wengophone-devel] New list and and web home are active
Vadim Lebedev wrote: Folks, The subejcts says it all. Take a look to www.qutecom.org i've subscribed all existing subscribes to the new list You you didnt't receive a welcome message in couple of hours it means i've goofed so please go to http://lists.qutecom.org/mailman/listinfo/qutecom-dev and subscribe manually I've already registered a channel on freenode: #qutecom @ freenode Thanks Vadim -- andreas 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] Qutecom or Wengo 2.2 Repo
Vadim Lebedev wrote: Cristofer, Please use qutecom 2.2 repo The repository is located here: http://hg.qutecom.org/ Thanks Vadim J. Christopher Pereira Area Informática IMATRONIX S.A. www.imatronix.com http://www.imatronix.com (09) 8573 4518 (32) 2768077 I am using the free version of SPAMfighter for private users. It has removed 34957 spam emails to date. Paying users do not have this message in their emails. Try SPAMfighter http://www.spamfighter.com/len for free now! ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com mailto:Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel ___ 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
[Wengophone-devel] Qutecom
Hi Vadim, I miss a simple html page on qutecom.org pointing out that it is a fork of wengophone and how to checkout the latest version with hg. If there is no progress with the page and new mailing list there should be at least some information on the page. -- 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
Re: [Wengophone-devel] WengoPhone release build issues
of the debug version of the # Boost library component. # Boost_${COMPONENT}_LIBRARY_RELEASE The absolute path of the release version of the # Boost library component # # Copyright (c) 2006-2008 Andreas Schneider [EMAIL PROTECTED] # Copyright (c) 2007 Wengo # Copyright (c) 2007 Mike Jackson # Copyright (c) 2008 Andreas Pakulat [EMAIL PROTECTED] # # Redistribution AND use is allowed according to the terms of the New # BSD license. # For details see the accompanying COPYING-CMAKE-SCRIPTS file. # # MESSAGE(STATUS Finding Boost libraries ) SET( _boost_TEST_VERSIONS ${Boost_ADDITIONAL_VERSIONS} 1.33 1.33.0 1.33.1 1.34 1.34.0 1.34.1 ) # # Check the existence of the libraries. # # This macro was taken directly from the FindQt4.cmake file that is included # with the CMake distribution. This is NOT my work. All work was done by the # original authors of the FindQt4.cmake file. Only minor modifications were # made to remove references to Qt and make this file more generally applicable # MACRO (_Boost_ADJUST_LIB_VARS basename) IF (Boost_INCLUDE_DIR ) #MESSAGE(STATUS Adjusting ${basename} ) IF (Boost_${basename}_LIBRARY_DEBUG AND Boost_${basename}_LIBRARY_RELEASE) # if the generator supports configuration types then set # optimized and debug libraries, or if the CMAKE_BUILD_TYPE has a value IF (CMAKE_CONFIGURATION_TYPES OR CMAKE_BUILD_TYPE) SET(Boost_${basename}_LIBRARY optimized ${Boost_${basename}_LIBRARY_RELEASE} debug ${Boost_${basename}_LIBRARY_DEBUG}) ELSE(CMAKE_CONFIGURATION_TYPES OR CMAKE_BUILD_TYPE) # if there are no configuration types and CMAKE_BUILD_TYPE has no value # then just use the release libraries SET(Boost_${basename}_LIBRARY ${Boost_${basename}_LIBRARY_RELEASE} ) ENDIF(CMAKE_CONFIGURATION_TYPES OR CMAKE_BUILD_TYPE) SET(Boost_${basename}_LIBRARIES optimized ${Boost_${basename}_LIBRARY_RELEASE} debug ${Boost_${basename}_LIBRARY_DEBUG}) ENDIF (Boost_${basename}_LIBRARY_DEBUG AND Boost_${basename}_LIBRARY_RELEASE) # if only the release version was found, set the debug variable also to the release version IF (Boost_${basename}_LIBRARY_RELEASE AND NOT Boost_${basename}_LIBRARY_DEBUG) SET(Boost_${basename}_LIBRARY_DEBUG ${Boost_${basename}_LIBRARY_RELEASE}) SET(Boost_${basename}_LIBRARY ${Boost_${basename}_LIBRARY_RELEASE}) SET(Boost_${basename}_LIBRARIES ${Boost_${basename}_LIBRARY_RELEASE}) ENDIF (Boost_${basename}_LIBRARY_RELEASE AND NOT Boost_${basename}_LIBRARY_DEBUG) # if only the debug version was found, set the release variable also to the debug version IF (Boost_${basename}_LIBRARY_DEBUG AND NOT Boost_${basename}_LIBRARY_RELEASE) SET(Boost_${basename}_LIBRARY_RELEASE ${Boost_${basename}_LIBRARY_DEBUG}) SET(Boost_${basename}_LIBRARY ${Boost_${basename}_LIBRARY_DEBUG}) SET(Boost_${basename}_LIBRARIES ${Boost_${basename}_LIBRARY_DEBUG}) ENDIF (Boost_${basename}_LIBRARY_DEBUG AND NOT Boost_${basename}_LIBRARY_RELEASE) IF (Boost_${basename}_LIBRARY) SET(Boost_${basename}_LIBRARY ${Boost_${basename}_LIBRARY} CACHE FILEPATH The Boost ${basename} library) GET_FILENAME_COMPONENT(Boost_LIBRARY_DIRS ${Boost_${basename}_LIBRARY} PATH) SET(Boost_${basename}_FOUND 1) ENDIF (Boost_${basename}_LIBRARY) ENDIF (Boost_INCLUDE_DIR ) # Make variables changeble to the advanced user MARK_AS_ADVANCED( Boost_${basename}_LIBRARY Boost_${basename}_LIBRARY_RELEASE Boost_${basename}_LIBRARY_DEBUG ) ENDMACRO (_Boost_ADJUST_LIB_VARS) #--- SET( _boost_IN_CACHE TRUE) IF(Boost_INCLUDE_DIR) FOREACH(COMPONENT ${Boost_FIND_COMPONENTS}) STRING(TOUPPER ${COMPONENT} COMPONENT) IF(NOT Boost_${COMPONENT}_FOUND) SET( _boost_IN_CACHE FALSE) ENDIF(NOT Boost_${COMPONENT}_FOUND) ENDFOREACH(COMPONENT) ELSE(Boost_INCLUDE_DIR) SET( _boost_IN_CACHE FALSE) ENDIF(Boost_INCLUDE_DIR) IF (_boost_IN_CACHE) # in cache already SET(Boost_FOUND TRUE) FOREACH(COMPONENT ${Boost_FIND_COMPONENTS}) STRING(TOUPPER ${COMPONENT} COMPONENT) _Boost_ADJUST_LIB_VARS( ${COMPONENT} ) FOREACH(COMPONENT) SET(Boost_INCLUDE_DIRS ${Boost_INCLUDE_DIR}) ELSE (_boost_IN_CACHE) # Need to search for boost SET(_boost_INCLUDE_SEARCH_DIRS C:/boost/include C:/Program Files/boost/boost_${Boost_REQUIRED_VERSION} # D: is very often the cdrom drive, IF you don't have a # cdrom inserted it will popup a very annoying dialog #D:/boost/include /sw/local/include ) SET(_boost_LIBRARIES_SEARCH_DIRS C:/boost/lib C:/Program Files/boost
Re: [Wengophone-devel] New repositories
Dave Neary wrote: Hi Vadim, Vadim Lebedev wrote: Anybody have an advice for a CMS to use for www.qutecom.org? Before we'd closed up shop, we were evaluating two: Drupal and WordPress. WordPress would probably be the most simple of the two - it allows you to create static pages easily, and of course allows you to have a normal blog interface to your news page, as well as allowing you to have member blogs (which could then be aggregated with Planet). I would suggest Wordpress too. I use Wordpress and trac at http://www.csync.org/ The code quality is good. It works with APC. It is easy to maintain... For mailing list management I suggest http://mlmmj.mmj.dk/ Cheers, Dave. -- 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
Re: [Wengophone-devel] [PATCH] imported patch wifi_phapi_WENGOPHONE_UA.patch
Darshaka Pathirana wrote: Hi! Hello, And the next question leads me to this: How to (how do you) build the wengophone release version in with an installer? Some old(?) mailling-list entries talk about nmake install but is that still the way to go (especially if using Visual Studio 2005)? There is a python script in the scripts directory which creates the installer. It would be easier to use CPack for this job :) Thanks for you help! Greetings, - Darsha -- 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
Re: [Wengophone-devel] G772 and P2P SIP/SIMPLE
Vadim Lebedev wrote: you can do hg update -r 0 command to get intial version of repository which should be the same wengophone_2.2 on SVN Does hg have a bisect function? I haven't found somthing like git-bisect. -- andreas 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] HomePage, Wiki, hg, repositories
giopas wrote: Hi crew, Hossa, probably I'm wrong, but I still don't know if the the new project has its own homepage with new doc, bug reports, wiki... I think the new project still has no name :) -- 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
Re: [Wengophone-devel] buildbot scripts
Klaus Darilion wrote: Hi Andreas! Hi Klaus, I tried to find out something about the mentioned AMR mode in speex, but could not find any information. Do you have more information about this? sorry wengophone's phapi has this mode. Search for PH_SPEEXWB_REPLACES_AMRWB in wifo. thanks klaus -- 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
Re: [Wengophone-devel] buildbot scripts
Vadim Lebedev wrote: Klaus Darilion wrote: Vadim Lebedev schrieb: Klaus Darilion wrote: Andreas Schneider schrieb: Klaus Darilion wrote: Hi Andreas! Hi Klaus, I tried to find out something about the mentioned AMR mode in speex, but could not find any information. Do you have more information about this? sorry wengophone's phapi has this mode. Search for PH_SPEEXWB_REPLACES_AMRWB in wifo. btw: does OW support AMR-NB too? Which mode - bandwidth-efficient or octed-aligend mode? regards klaus Folks on this AMR issue phapi supports AMR NB and WB as a plugin module Does this mean that there is an AMR plugin available? part of OW? klaus wifo/phapi/phcodec-amr-wrapper.c It would be great if we could remove wifo/phapi/amr wifo/phapi/amrnb wifo/phapi/amrwb and compile amr support if the libraries are found. This would remove one problematic codec from the softphone. Vadim -- 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
Re: [Wengophone-devel] buildbot scripts
Vadim Lebedev wrote: Folks on this AMR issue phapi supports AMR NB and WB as a plugin module the PH_SPEEXWB_REPLACES_AMRWB stuff is simply an ugly hack to use AMR-WB payload code to transport SPEEX WB codec. It comes frm times when Wengo platform refused to operate in pass-thru mode for unknow payload codes So, would it be possible to get rid of the complete AMR code? Isn't speex and gsm enough and maybe some other free (as in free speech) codecs. Thanks Vadim -- 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] V4L2
For the TODO list: Improve v4l2 support. http://www.linuxtv.org/news.php?entry=2007-06-28.tmerle http://www.linuxtv.org/v4lwiki/index.php/V4L2UserspaceLibrary or http://www.quickcamteam.net/software/libwebcam -- 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
Re: [Wengophone-devel] buildbot scripts
Vadim Lebedev wrote: This is a request for (ex-)members of the Wengo team, Hi, Folks, maybe sombedy have a copy of buildbot scripts I'd like to install buildbot on our server it would be great to build it in the openSUSE buildservice. http://en.opensuse.org/Buildservice (You can build against openSUSE, Fedora, Mandriva, Ubuntu, Debian, Windows cross compiling, ...) The problem are some libraries WengoPhone is using. http://www.penguin.cz/~utx/amr http://www.ffmpeg.org/ Speex has a amr mode to emulate the codecs and maybe we could replace ffmpeg. ilbc could be a problem too. Thanks Vadim -- 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
Re: [Wengophone-devel] Link-Problem with Debian multimedia libs
Ralf Schlatterbeck wrote: On Wed, Jan 30, 2008 at 10:20:20PM +0100, Andreas Schneider wrote: Ralf Schlatterbeck wrote: I'm trying to build wengo 2.2 branch against etch packages from http://www.debian-multimedia.org (newer multimedia packages not found in core debian etch) and fail with missing symbols on the final linking. (Thanks to Darsha for helping out with cmake details). Missing symbols are img_resample_init, img_resample, img_resample_close, img_convert normally found (in stock debian) in libavcodec installed from libavcodec-dev. Is this a change in libavcodec api that wengo hasn't followed yet? Should I go back to the debian etch libs (which *do* have these symbols)? ffmpeg api has changed you need libswscale and swscale.h I see. I've now successfully built against the stock debian libs which don't have this api change yet. I guess for making it run with newer ffmpeg, code in wengo has to be changed, too, or is it enough to link against another lib (and use another include file)? The changes are already done. I works just fine for me. If CMake finds swscale it uses the new api. Thanks Ralf -- 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
Re: [Wengophone-devel] patchset wengophone-2.2 (r13252)
Darshaka Pathirana wrote: Hi Andreas! Hi Darshaka, - wengophone/src/buildid/CMakeLists.txt The Preprocessor Definition DD_BUILDID had two LL at the end (I don't know why) but they should be an integer. The patch fixes that. #define FOO 42LL means that FOO is a long long. Current date and time is for example 20070127132638, this doesn't fit into an integer you need a 64bit variable. That's why the function in wengophone/src/WengoPhoneBuildId.cpp returns a long long. const unsigned long long WengoPhoneBuildId::getBuildId() { return DD_BUILDID; } So #define DD_BUILDID 2007012713263LL is right! Hmm... Strange. I've just recompiled owbuildid. Now it seems to work with these LL at the end (with an warning though). But thanks for clearifing this issue. I have still one more questions: At the beginning of build process I get: -- Rebuild All started: Project: owbuildid, Configuration: Debug Win32 -- Deleting intermediate and output files for project 'owbuildid', configuration 'Debug|Win32' Building Custom Rule C:/Projects/wp-2.2/wengophone/src/buildid/CMakeLists.txt Subversion (svn) command line not found, it is recommended to install it -- OS: Windows-5.0 -- Processor: x86 -- Compiler: C:/Program Files/Microsoft Visual Studio 8/VC/bin/cl.exe -- Build type: Debug -- Build tool: C:/PROGRA~1/MICROS~3/Common7/IDE/VCExpress.exe -- Build directory: C:/Projects/wp-2.2/build/debug -- svn revision: 13253 -- Time: [snip] I believe the date-time used by the BUILDID comes from the time field which - in my case - is empty. What do I have to do get that value? It seems that OWGetCurrentDateTime.cmake respectivly a output in getcurrentdatetime.cpp but I fail to decode what's going on in there. (Looks like the cpp is compiled and run out of the cmake-build-process; does that work under Windows?) I'm not a windows user. If you're on windows, you're on your own :) (Just for reference: I always had the svn revision 0 until I installed the command-line version of subversion. After that the svn revision was detected correctly.) Yes, that's how it is designed. 2. The Visual C++ compiler option -D do strip the quotes on the command line[2] so this must be handled by a define in phapi.c. That's bad, have you tried to escape them? There should be another way to do that. -DWENGOPHONE_UA=\wengo/v1/wengophoneng/wengo/rev${SVN_REVISION}/trunk/\ or -DWENGOPHONE_UA='wengo/v1/wengophoneng/wengo/rev${SVN_REVISION}/trunk/' or -DWENGOPHONE_UA='wengo/v1/wengophoneng/wengo/rev${SVN_REVISION}/trunk/' Yeah, I also do not like this solution. I've tried your suggestions and a lot of other things but I was not able to get around it. Any Visual C++-Crack who knows how to fix that? We should create config.h files instead of passing defines via the commandline. Maybe you want to do that :) config.h.cmake and ConfigureChecks.cmake is needed. See srtp. I'll take Thomas' latest revision and work on that one. After that I will come back and let the patches be reviewed again... That would be great. It would be great if Thomas would attend to this discussion :) Greetings, - Darsha -- 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
Re: [Wengophone-devel] Openwengo REPO conversion
Darshaka Pathirana wrote: Hi Vadim! On 25.01.2008 20:18, Vadim Lebedev wrote: I' Independently i'm struggling with the fact that mercurial does not support subprojects so i'd like to pickup your brains for suggestions on how to organize mercurial repos for the openwengo project I would like to help you but unfortunatly I am not (yet) completely aware of the full source code. If you're able to give me some hints and tell me what YOU mean by subprojects, that would be really helpfull. I also have some questions regarding the code policy: - The openwengo-project holds internal copies of the source code of a various number of libraries. Will that change? Is that (still) a good idea? Subprojects are for example owutil (ow macros for cmake), webcam, util etc. Everything which is a external in subversion atm. 2.2 has no externals afaik. - If splitting up the project, will the history of each file remain? I know only git and it imports the whole history of each file. I think hg will do the same. - maybe more... Greetings, - Darsha -- 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
Re: [Wengophone-devel] some thoughts on submitting patches
Darshaka Pathirana wrote: Hi! Hello, - How to create the patch? svn diff file foo.patch if you fix a bug in N source files of a module use. svn diff file..fileN foo.patch Don't submit everything as one big patch. - What should be the filename of the patch? I name them after the subject. fix_gcc43_warnings.patch for example - How is the patch submitted? Attach them to a bug or add them as an attachement to an email. The first question should be easy to answer: - Use svn diff or create a patch with TortoiseSVN (or even use diff -u) The second question is not that easy. My suggestion (if anybody cares): - {OrigFilename}_r{svnrevision}_{patchName}-{patchVersion}.diff|patch The third question is also not as easy as it seems: As Attachment? attachement What should be the subject? [PATCH] - {OrigFilename}_r{svnrevision}_{patchName}-{patchVersion} [PATCH] - Subject of the patch Git has a special approach for commit messages, I think it is the same for hg. The first line is a summary of the patch, max 60 chars. Then an empty line and a description of the patch. I also like the idea of [3] of adding a patch header on each patch, but I may be wrong. Yes, this makes it easier for the reviewer. I do that normally. With git you do git-format-patch origin/master and you get what you want. I hope hg can do the same. What do you maintainer and longtime contributors think? Is that too much overkill or would you like to stick to some guidelines? I would love to hear your opinions. Thank you! git does everything which you asked for. Hopefully hg behaves the same. The important thing is that you write good commit messages. Greetings, - Darsha -- 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
Re: [Wengophone-devel] Link-Problem with Debian multimedia libs
Ralf Schlatterbeck wrote: Hi I'm trying to build wengo 2.2 branch against etch packages from http://www.debian-multimedia.org (newer multimedia packages not found in core debian etch) and fail with missing symbols on the final linking. (Thanks to Darsha for helping out with cmake details). Missing symbols are img_resample_init, img_resample, img_resample_close, img_convert normally found (in stock debian) in libavcodec installed from libavcodec-dev. Is this a change in libavcodec api that wengo hasn't followed yet? Should I go back to the debian etch libs (which *do* have these symbols)? ffmpeg api has changed you need libswscale and swscale.h Ralf -- 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
Re: [Wengophone-devel] news from wengo
Vadim Lebedev wrote: Hello OpenWengo develppers and users! I'm the person who will coordinate openwengo development at MBDSYS I'd like to thank Wengo for all the efforts they've done to develop OpenWengo project and for the confidence in our ability to keep the project striving. Hi, thats really a good news. Here is our very short term plan: 1) We're working to switch openwengo repository to use mercurial dvcs (http://www.selenic.com/mercurial) When we'll finish (hopefully this week) i'll publish the new repository URL That's what I don't like. I would prefer git over mercurial. Specially cause of performance (git-gc and git protocol) and data integrity (git-fsck). -- 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
Re: [Wengophone-devel] patchset wengophone-2.2 (r13252)
Darshaka Pathirana wrote: Hi! Hello, Success! great! Finally I was able to fully build the latest wengophone-2.2 revision with Visual Studio 2005 Express Edition! First of all I would like to refine my first post[1] with a few corrections: 1. I used wengophone-2.2 (rev 13252) instead of (rev 13237) 2. You actually you do NOT need to change the C:\Program Files\Microsoft Visual Studio 8\Common7\Tools\vsvars32.bat file for this project. vsvars32.bat actually only needs to be modified if you want to use the Platform SDK and/or DirectX SDK and want to compile your programs on the command line. So just let all of the given environment variables be set by the system and add the Include and Lib-paths as described in Visual Studio C++ 2005. Ok. As promised I attached my patchset for revision 13253 of wengophone-2.2. I'll try to explain what happened and what I have changed. I also may have questions and I by no means think that this is the ultimate solution. So if you think you can pinpoint what could be done better I would be very glad! Basically you can follow steps 1 to 7 from my first post[1] except for my corrections above. Let's continue with the next steps: 8. Patch the files As mentioned just apply my attached patchset (wengophone_2.2_r13252_dpat-2.diff). This can easily be done with TortoiseSVN. Right-click on the wengophone-2.2 folder, click Apply patch.. and choose the file. After that you will see a popup file patches. Just right-click on it and choose Patch all. Done! 9. Configure wengophone (create Visual Studio Project files): 9a. Run C:\Projects\wengophone-2.2\build\create_vcproj-VC80.bat You can actually just double-click on it. vsvars32.bat is called out of it. This should create the Visual Studio project files. 10. Open the project The Visual Studio Solution is then located in the build-directory. After opening it you'll notice a popup The solution already conatains an item named 'lrelease'. That's not critical so just ignore it! (Maybe somebody knows how to get rid of it.) 11. Build wengophone You can either build the whole solution, the project ALL_BUILD or the project WengoPhone. The safest bet would be to build the whole solution. Actually all of Visual Studio project files / properties are also rebuild (by some CMake-Magic) so it might be necessary to build wengophone a second time. In fact you have to rebuild those projects where you changed any of the cmake-files (or at least have to wait until the initial configuration is done and start over). After some time (go out and meet some friends ;) ) you should see a fine built wengophone.exe in your build-directory. 12. Start it and have fun debugging... Smaller patches than one big file would be nice. Additional notes on my patchset: - libs/3rdparty/qt4/CMakeLists.txt Since a version of Qt 4.x the DLLs of the lib are now ending with a 4. I have changed that accordingly. Are you sure that this is the case for all released Qt version. Maybe the others should stay in the code. I think if the file doesn't exist, it would stop to work. - libs/owutil/util/CMakeLists.txt - libs/webcam/CMakeLists.txt - wifo/phapi-util/CMakeLists.txt The lib files of these projects are not created without these definitions. I think this should be wrapped in an if (WIN32) endif (WIN32) - owbuild/owbuild/OWCreateProjectBinary.cmake This was tricky and I am still not absolutly sure about it. This patch now enables the post-build-copy-process to copy the DLL and PDB files from the correct directory (by taking the right buildtype (debug vs. release) into account). Maybe someone can take a special look at this one. Thanks! Yes, the files should be copied to the build type directory (release, debug) - wengophone/src/buildid/CMakeLists.txt The Preprocessor Definition DD_BUILDID had two LL at the end (I don't know why) but they should be an integer. The patch fixes that. #define FOO 42LL means that FOO is a long long. Current date and time is for example 20070127132638, this doesn't fit into an integer you need a 64bit variable. That's why the function in wengophone/src/WengoPhoneBuildId.cpp returns a long long. const unsigned long long WengoPhoneBuildId::getBuildId() { return DD_BUILDID; } So #define DD_BUILDID 2007012713263LL is right! - wifo/owsl/src/core/owsl_address.c OWSL_FUNC_DEF (which is definded as __declspec(dllimport)) is already set in the header. No need to do that again. - wifo/phapi/CMakeLists.txt There two patches in here... 1. The lib file is not created without this definition. Should be wrapped into if (WIN32) 2. The Visual C++ compiler option -D do strip the quotes on the command line[2] so this must be handled by a define in phapi.c. That's bad, have you tried to escape them? There should be another way to do that. -DWENGOPHONE_UA=\wengo/v1/wengophoneng/wengo/rev${SVN_REVISION}/trunk/\ or
Re: [Wengophone-devel] Why is it so calm
John Draper wrote: Will it be possible to find a new hosting server for WengoPhone? Wish I could help, I'm having hosting problems myself. Hosting is not the problem, I already have a git repository for wengophone-2.2. The problem is to find a maintainer. I'm not a C++ programmer and I don't have the time to do this job. Aurélien, Dave I hope you will find a new job soon. If you ever plan to work again on WengoPhone, let me know :) All the best and merry christmas, -- 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
Re: [Wengophone-devel] [PATCH] Using Psi idle detection system
Aurélien Gâteau wrote: Aurélien Gâteau a écrit : Hello, Hi, You might have noticed that our idle detection system is not really working. Its main problem is that it does not work when the application does not have the focus, making it rather useless. Attached patches contains a copy of Psi 0.11 idle detection system, which works much better by detecting idle status using OS specific code. It works on my Linux box (I need to test it on Windows and MacOS X) FYI, after fixing compilation on Windows and MacOS X, I committed it. Works just fine for atm ... :) Aurélien -- 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
Re: [Wengophone-devel] Bad interaction with Qt themes
Ludovico Cavedon wrote: Aurélien Gâteau wrote: I can reproduce the cleanlook bug (need to have a further look at it), but I never encountered the plastique one. I tried with KWin and Beryl on a Ubuntu Feisty. Is it 100% reproducible for you? Hi, I can reproduce both. I am under amd64 architecture, Ubuntu gutsy. Binaries from the openwengo website do not exhibit this problem (note that they are compiled for 32 bit arch). Aurélien I told you about my problems with the configuration window being to huge. The height is about 2000px or much more. I think it is the same problem. If I compile at 64 bit, I get the issue when start wengophone and compiz is running. without compiz ... Bye, Ludovico -- 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
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/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
Re: [Wengophone-devel] New in this!!
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
Re: [Wengophone-devel] Logging committed
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
[Wengophone-devel] Re: [Wengophone-commit] r12973 - owbuild/branches/wengophone-2.2/owbuild
[EMAIL PROTECTED] wrote: Author: agateau Date: 2007-10-10 14:49:43 +0200 (Wed, 10 Oct 2007) New Revision: 12973 Modified: owbuild/branches/wengophone-2.2/owbuild/FindBoost.cmake Log: * (feature) New variable: BOOST_VERSION. Hi Agateau, what do you think about using the BOOST_LIB_VERSION from boost/version.cpp for detecting the libraries. ... 105 if (MSVC71) 106 if (CMAKE_BUILD_TYPE STREQUAL Debug) 107 set(BOOST_LIBRARIES_SUFFIXES 108 -vc71-mt-gd-${BOOST_LIB_VERSION} 111 ) ... -- 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
Re: [Wengophone-devel] Re: [Wengophone-commit] r12973 - owbuild/branches/wengophone-2.2/owbuild
Aurélien Gâteau wrote: On Wednesday 10 October 2007 15:25:36 Andreas Schneider wrote: [EMAIL PROTECTED] wrote: Author: agateau Date: 2007-10-10 14:49:43 +0200 (Wed, 10 Oct 2007) New Revision: 12973 Modified: owbuild/branches/wengophone-2.2/owbuild/FindBoost.cmake Log: * (feature) New variable: BOOST_VERSION. Hi Agateau, what do you think about using the BOOST_LIB_VERSION from boost/version.cpp for detecting the libraries. ... 105 if (MSVC71) 106 if (CMAKE_BUILD_TYPE STREQUAL Debug) 107 set(BOOST_LIBRARIES_SUFFIXES 108 -vc71-mt-gd-${BOOST_LIB_VERSION} 111 ) ... Sounds like a good idea indeed. It would avoid having multiple suffixes which need to be updated everytime a new Boost is out. The problem are the boost path suffixes for the include directory. Maybe we can try a regex here. Aurélien -- 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
Re: [Wengophone-devel] New committer
Sean Bride wrote: Our requirements are pretty specific: * Source control system must be cross-platform, and fast Git is cross-platform and fast. It runs perfect on windows now: http://code.google.com/p/msysgit/ * A central canonical source for the software is essential Git does canonical too. * An easy migration path from our existing system (svn) Git does this also (git-svn clone https://dev.openwengo.org/svn/openwengo/wengophone-ng/trunk; for trunk), I've just cloned the whole OW trunk repository in a git one in a couple of minutes with all the commits history. The cross-platform requirement rules out git for the moment, the best distributed candidate is Mercurial, then perhaps Bazaar-NG. False, it runs fine on windows see previous link. (and Bazaar is really slow). Subversion fulfils its requirements very well - it is cross-platform, allows us to manage access rights for developers, Well with Git, you don't need to worry about access rights for developers, you don't need to waste a lot of time on politics and trying to figure out who's smart enough to commit and who's not. It will save OW devs lot of time actually. provides a canonical source for the source code, again, you can have a central repository with Git, it's even very easy to use. Actually Git is a lot simpler than SVN to use. and was very easy for developers to use from the start because of both windows GUI front ends Git comes with gitgui and gitk to view and commit on all platforms. The arguments for investing time effort into moving away from our existing system would need to be very compelling, and so far I haven't heard a really compelling one. ok how about it saves time and resources for OW developers because it is so much easier to manage, people will be able to commit and send patches more easily and decentralized is just the natural way to do things in the Open Source community. I've never met anybody switching to Git coming back to SVN, it's just superior and so much nicer to use, there's just no turning back. Is git submodule already done? We need this feature. We make heavy use of svn externals. -- andreas 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] Why WengoPhone-NG switched from SCons to CMake
Dave Neary wrote: Hi, Hi, There are two answers: 1. Scons was slooow - particularly recompiling. The CMake based system goes much faster. 2. CMake has started to be widely adopted - perhaps more than scons. It's easily available in most distributions, doesn't require installing Python if you're on Windows, and that all makes for a lower barrier to entry for hackers who want to compile the project. 3. It is easier to write CMake files than SCons. 4. CMake is more flexible. It creates Makefiles, KDevelop files, MSVC files, XCode files ... 5. It has x86_64 support by default It is simply better. -- andreas ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] New committer
Sean Bride wrote: I don't understand why wengo devs don't want to switch to something more powerful like git or mercurial where everybody can commit easily and send nice patches and actually *help* the openwengo more efficiently. Don't you want the community to help the project? why are you being so stubborn about it? I don't get it please educate yourself about Git and Mercurial and stop using SVN which is a pain for people that want to actually help you (for free): http://youtube.com/watch?v=4XpnKHJAok8 http://www.stonehenge.com/pic/Git-2.0.3-to-be.pdf http://blogs.gnome.org/shaunm/2007/09/17/git-for-gnome/ http://blog.cmsmadesimple.org/2007/09/13/using-git-for-core-development/ http://www.betaversion.org/~stefano/linotype/news/106/ Decentralized SCM are more democratic, faster and more efficient and doesn't make people (that want to give *you* some of their free time) feel like they're inferior to the other members of the community that have the divine commit access. http://article.gmane.org/gmane.comp.voip.wengophone.devel/5096/match=git Thanks for reading, Sean -- 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] 2.2 and ALSA
Hi, Alec: I'm running latest 2.2 at the moment. Playing sound works just fine but as soon as I try to do a test call, I get the following message: (debug) 18:04:29 void phapiLogFunction(OWPL_LOG_LEVEL, const char*): must wait: Resource temporarily unavailable I have no time to look at the code at the moment. I this a message of the phmedia-alsa driver? What resource is temporarily unavilable? -- 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
Re: [Wengophone-devel] [Fwd: [opensuse-packaging] GCC 4.3 transition and fallout in your packages]
Dave Neary wrote: Hi, Andreas Schneider wrote: For your interest. Phapi will be a problem or better most of the wifo tree. ... 1) Missing includes. Weird - implicit function prototypes aren't a standard breach by any means... is there a compiler flag to turn this error off? If you have missing includes. So it says: implicit declaration of function xxx. This could lead to segfaults on x86_64. So this will be an error now. I don't think that this is bad, it just forces you to do cleaner coding. Although it would be nice to clean the warnings out of wifo... I will do this if I find some time. Cheers, Dave. -- 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] [Fwd: [opensuse-packaging] GCC 4.3 transition and fallout in your packages]
For your interest. Phapi will be a problem or better most of the wifo tree. -- andreas -- http://www.cynapses.org/ - cybernetic synapses ---BeginMessage--- The upcoming transition to GCC 4.3 will cause some common problems in C and C++ source to become compile-time errors. You investigate if your Factory package is affected by looking at the home:dirkmueller:playground:gcc43 project which is currently rebuilding (most of) Factory with GCC 4.3. Common problems include: 1) Missing includes. The include dependencies of the standard library headers were cleaned up a lot and a lot less unneeded dependencies are pulled in. This results in errors like Geometry.cpp: In member function 'const Magick::Geometry Magick::Geometry::operator=(const std::string)': Geometry.cpp:191: error: 'strcpy' was not declared in this scope make[3]: *** [Geometry.lo] Error 1 which hints at that you should include cstring, the C++ standard include name of the C string.h header. The rule of thumb is to look in which C header the missing function is in and then include the C++ variant which has a 'c' prepended and the '.h' stripped off. This is 90% of all errors we currently see with C++ programs. 2) There are extra warnings with GCC 4.3 and you use -Werror. You simply need to fix them. 3) More picky preprocessor: main.cpp:182:7: error: extra tokens at end of #endif directive the preprocessor diagnoses #endif foo use #endif /* foo */ instead. 4) C99 inline semantics changes. If you use 'extern inline foo(' in headers and build with either -std=c99 or -std=gnu99 then you will probably face linker errors complaining about duplicate symbols. If you want to fix this in a way that is compatible with GCC 4.3 and previous versions use something like the following: extern inline #ifdef __GNU_STDC_INLINE__ __attribute__((__gnu_inline__)) #endif foo( which will preserve the previous semantics. If you do not care about compatibility with older GCC and want to use C99 semantics simply remove the 'extern' qualifier on inline functions defined in headers. 5) If you see something like /usr/include/zypp/Bit.h:86: error: declaration of 'typedef struct zypp::bit::MaxBits_IntT zypp::bit::Range_IntT, _begin, _size::MaxBits' /usr/include/zypp/Bit.h:52: error: changes meaning of 'MaxBits' from 'struct zypp::bit::MaxBits_IntT' you did something like template class T struct Foo : public FooBarT { typedef Foo::FooBarT FooBar; ... this is invalid C++. Use a different typedef-name here: typedef Foo::FooBarT FooBar_t; - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ---End Message--- 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] Getting rid of PortAudio support?
Aurélien Gâteau wrote: Hello, Hi, Since PortAudio support is currently not really maintained and Alsa support is getting more reliable. I was wondering if anyone would object getting rid of PortAudio before 2.2 is out. What's your opinion on this? Does the PortAudio version performs better than the Alsa version on your hardware? Portaudio caused always more trouble than it helped. Remove it! -- andreas ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] cmake fails building wengophone 2.1 on windows
Johan Öhrn wrote: Hi, Hello, I'm following the build instructions trying to build wengophone for windows. I want to fix ticket #1766! I have checked out the following source: https://dev.openwengo.org/svn/openwengo/wengophone-ng/branches/wengophone-2.1 At first I got these kind of errors: CMake Error: Error in cmake code at D:/JOHAN/WengoPhone/branches/wengophone-2.1/CMakeLists.txt:26: SUBDIRS Incorrect SUBDIRS command. Directory: libs/3rdparty does not exists. Current CMake stack: [1] D:/JOHAN/WengoPhone/branches/wengophone-2.1/CMakeLists.txt CMake Error: Error in cmake code at D:/JOHAN/WengoPhone/branches/wengophone-2.1/CMakeLists.txt:31: SUBDIRS Incorrect SUBDIRS command. Directory: libs/3rdparty/portaudio does not e xists. You didn't checkout the source completely. All the external links didn't get checked out. That's the reason why it doesn't work. Checkout again. I should look like this: [EMAIL PROTECTED]:~/workspace/source/projects/wengophone-2.2 svn up Ulibs/sound/include/sound/AudioDevice.h Ulibs/sound/include/sound/Sound.h Ulibs/sound/src/linux/Sound.cpp Ulibs/sound/src/AudioDevice.cpp Ulibs/sound/src/unix/Sound.cpp Alibs/sound/src/Sound.cpp Ulibs/sound/CMakeLists.txt Uwengophone/src/presentation/qt/config/QtAudioSettings.cpp Uwengophone/src/presentation/qt/chat/ChatMainWindow.ui Uwengophone/src/presentation/main.cpp Uwengophone/nsis/files_install.nsi Uwengophone/nsis/installer.nsi Ucrashreport/main.cpp Fetching external item into 'owbuild' Updated external to revision 12713. Fetching external item into 'wifo' Updated external to revision 12713. Fetching external item into 'libs/3rdparty' Updated external to revision 12713. ... ... so I just created the directories which was not found. Now I get this output running cmake: D:\JOHAN\WengoPhone\branches\wengophone-2.1\buildbuild_nmake-release.bat D:\JOHAN\WengoPhone\branches\wengophone-2.1\buildcmake .. -DCMAKE_BUILD_TYPE=Re lease -G NMake Makefiles -- Check for CL compiler version -- Check for CL compiler version - 1400 -- Check if this is a free VC compiler -- Check if this is a free VC compiler - no -- Check CL platform -- Check CL platform - 32 bit -- Check for working C compiler: D:/Program Files/Microsoft Visual Studio 8/VC/b in/cl.exe -- Check for working C compiler: D:/Program Files/Microsoft Visual Studio 8/VC/b in/cl.exe -- works -- Check size of void* -- Check size of void* - done -- Check for working CXX compiler: D:/Program Files/Microsoft Visual Studio 8/VC /bin/cl.exe -- Check for working CXX compiler: D:/Program Files/Microsoft Visual Studio 8/VC /bin/cl.exe -- works Subversion (svn) command line not found, it is recommended to install it -- OS: Windows-5.1 -- Processor: x86 -- Compiler: D:/Program Files/Microsoft Visual Studio 8/VC/bin/cl.exe -- Build type: Release -- Build tool: nmake -- Build directory: D:/JOHAN/WengoPhone/branches/wengophone-2.1/build/release -- svn revision: 0 -- Time: 20070920163945 CMake Error: httptunnel: openssl_INCLUDE_DIRS and openssl_INCLUDE_DIR empty, che ck that openssl is declared before httptunnel -- Configuring done D:\JOHAN\WengoPhone\branches\wengophone-2.1\buildnmake Microsoft (R) Program Maintenance Utility Version 8.00.50727.762 Copyright (C) Microsoft Corporation. All rights reserved. NMAKE : fatal error U1064: MAKEFILE not found and no target specified Stop. D:\JOHAN\WengoPhone\branches\wengophone-2.1\build What must I do so that cmake does not fail? Thanks! / Johan _ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] cmake fails building wengophone 2.1 on windows
Johan Öhrn wrote: Hi, Hello, I have set the following environment variables: @set BOOSTINCLUDEDIR=D:\L\INCLUDE\boost\boost_1_34_1 @set BOOSTLIBDIR=D:\L\INCLUDE\boost\boost_1_34_1\lib @set BOOST_ROOT=D:\L\INCLUDE\boost\boost_1_34_1 please post a directory list of the libraries. I need the names of the dll files. Cheers, -- andreas ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Connection problem for windows client
Iñaki Baz Castillo wrote: El Wednesday 19 September 2007 07:24:09 Mangesh Kulkarni escribió: Hello, I'm newbie for wengo and trying to connect using wengophone 2.1.2 client. Hi, does Microsoft Office Outlook 12.0 set blue fonts by default when composing a mail? Please, don't use HTML, formated or colored text in maillist because it's really uncomfortable for people reading lot of mail. ;) http://www.guckes.net/mail/edit.html :) ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] AMR questions
Klaus Darilion wrote: Hi! I wonder how you deal with AMR license restrictions - does Wengo pays for the AMR license or is it the users task to get an AMR license? Hello, WengoPhone is developed in Europe, so we don't have any software patents here. If the user lives in a country which has software patents like the USA, the user needs a license to use WengoPhone. This is a problem we should discuss. http://www.penguin.cz/~utx/amr states: AMR codecs incorporate several patents, held by Ericsson, Universite de Sherbrooke (VoiceAge) and Nokia. VoiceAge claims to provide patent portfolio for AMR codecs. Depending on law in your country, manufacturers and developers may need to get a license. Because it is a shared library, you may need a special contract for each one application, which links against this library, directly or indirectly. -- 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
Re: [Wengophone-devel] wengophone 2.2 Beta
Dave Neary wrote: Hi all, Hi Dave, I'd like to have a new beta release of the WengoPhone 2.2 branch next week (probably Thursday). I would just release a new alpha version. I think we should update wengophone to use libpurple instead of gaim before we got to beta state. Normally beta means no more features and just bugfixes. -- 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
Re: [Wengophone-devel] Wengo 2.2 --- V4L2 --- UVC --- Logitech 5000Pro
Michael Werner wrote: Hali, hallo Hi, I tested the latest build (WengoPhone-2.2-minsizerel-alsa-12559) with my Logitech 5000Pro. Now it seems that the V4L2 implementation works. The Webcam lamp lights. I have a Logitech Ultra Vison webcam using the uvcvideo driver. I have sometimes the problem that after a boot if I try the webcam I get these failures. If I reattach the USB cable it works just fine. Could you please do this and test again. Thanks, -- andreas But i can't see a correct picture. The Logs: t: Capture (warn) 14:49:49 virtual WebcamErrorCode V4L2WebcamDriver::setPalette(pixosi): Failed settings pixel format. (info) 14:50:45 virtual void PhApiWrapper::setCallsEncryption(bool): Set call encryption to:0 (info) 14:50:45 virtual void PhApiWrapper::setCallsEncryption(bool): Set call encryption to:0 (warn) 14:51:32 void V4L2WebcamDriver::checkDevice(): VIDIOC_G_FMT failed (warn) 14:51:32 void V4L2WebcamDriver::checkDevice(): Detecting minimum resolution with VIDIOC_S_FMT failed (warn) 14:51:32 void V4L2WebcamDriver::checkDevice(): VIDIOC_G_FMT failed detecting minimum resolution (warn) 14:51:32 void V4L2WebcamDriver::checkDevice(): Detecting maximum resolution with VIDIOC_S_FMT failed (warn) 14:51:32 void V4L2WebcamDriver::checkDevice(): VIDIOC_G_FMT failed detecting maximum resolution (warn) 14:51:32 void V4L2WebcamDriver::readCaps(): Reading capabilities failed. No V4L2 device (info) 14:52:18 virtual void PhApiWrapper::setCallsEncryption(bool): Set call encryption to:0 (warn) 14:52:48 virtual WebcamErrorCode V4L2WebcamDriver::setResolution(unsigned int, unsigned int): Failed settings picture dimensions. (warn) 14:52:48 virtual WebcamErrorCode V4L2WebcamDriver::setPalette(pixosi): Failed settings pixel format. Is the V4L2 UVC implementation in wengo finished? ___ 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] WengoPhone has V4L2 support now
Andreas Schneider wrote: Hi List, I've committed the Video4Linux2 patches from Jarosław Lewandowski (ticket #1470) to the wengophone 2.2 branch and got my webcam running (uvcvideo). Some webcams need the framerate set after the resolution was set. Hi, I've committed new changes to the v4l2 interface. Some fixes and some checks. I got it working with my webcam and the new libswcale from ffmpeg! http://www.cynapses.org/tmp/wengophone/wengophone-v4l2-swscale.png The problem is that it doesn't work out of the box for my webcam yet. We try to set it to YUV420P, but I have to set it to YUYV first to get it working. I think I have to enumerate over the supported formats and check for one we could convert with pixertool. Then set the one we try to force (YUV420P). If you have a webcam please test. I have no feedback yet. Please test wengophone 2.2 if you have a v4l2 webcam and give me feedback! -- 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
Re: [Wengophone-devel] ALSA support in WengoPhone and PhApi
Ludovico Cavedon wrote: Gianluca Sforna wrote: quote 6. If you have an application that uses ALSA, please make sure that it doesn't hardcode ALSA driver names (i.e. something like hw:0), it should use default instead, which is now being redirected to pulse, our plugin for libasound. Hardcoding ALSA device names (besides default) is a bug in your application anyway, so here you have yet another reason to fix that! /quote Yes, sounds more than reasonable. Using hw or plughw we bypass the user configuration in .asoundrc, and this is not nice. Moreover it should be not a task of the application to select the audio configuration, which can be quite complex. See this message and the other s from the thread: http://lalists.stanford.edu/lad/2002/05/0111.html Applications should allow to choose between *virtual* PCM devices (like default is). However, using the ALSA API which is mostly used (1.0.13) it is not possible (as far as I could understand: I am not an expert, I spent some time gathering info); it is possible only starting from API 1.0.14. In the meanwhile, I think the best choice would be do as mstute suggested: use the default PCM device by default (this would not break compatibility with PulseAudio, etc), but allow the user to choose a specific audio card (i.e. if they want to use a USB headset). Yes, I think this should be the way to go. It would be nice if we have support for both the old API and the new API. Regards, Ludovico -- andreas ___ 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] Re: Wengo 2.1.2 Mac Intel
Dave Neary wrote: Hi Aymerick, I've copied the developer's mailing list with your problem - thank you for the information, and we'll do our best to diagnose it out ASAP. Someone reported today. [12:18:12] mETz hi [12:19:26] mETz Who packaged the intel mac build of 2.1.2? It's a complete mess, includes Qt 4.1.x but the binary depends on Qt 4.3.x, also library paths are wrong. -- andreas Cheers, Dave. M-Rick wrote: Hi The OpenWengo version 2.1.2 is crashing on Mac OS X Intel. It will not launch. This is a copy of the Crash Report from the Console : Host Name: Ordinateur-de-Aymeric-GILLAIZEAU-MacBook-Pro Date/Time: 2007-08-27 13:44:09.105 +0200 OS Version: 10.4.10 (Build 8R2218) Report Version: 4 Command: WengoPhone Path:/Users/aymeric/Desktop/WengoPhone.app/Contents/MacOS/WengoPhone Parent: WindowServer [61] Version: ??? (2.1.2) PID:310 Thread: Unknown Link (dyld) error: Library not loaded: QtCore.framework/Versions/4/QtCore Referenced from: /Users/aymeric/Desktop/WengoPhone.app/Contents/MacOS/WengoPhone Reason: image not found *Nous n'héritons pas de la terre de nos parents, nous empruntons celle de nos enfants.* */Antoine de Saint-Exupéry/* -- 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] Re: [Wengophone-commit] r12365 - owbuild/branches/wengophone-2.2/owbuild
Hi, Philippe why did you remove the documentation? -- andreas [EMAIL PROTECTED] wrote: Please, do not reply to this mailing list, use wengophone-devel instead. Author: pbernery Date: 2007-08-23 11:31:59 +0200 (Thu, 23 Aug 2007) New Revision: 12365 Modified: owbuild/branches/wengophone-2.2/owbuild/FindBoost.cmake Log: * (buildfix) compilation fix for Mac OS X Modified: owbuild/branches/wengophone-2.2/owbuild/FindBoost.cmake === --- owbuild/branches/wengophone-2.2/owbuild/FindBoost.cmake 2007-08-22 15:22:16 UTC (rev 12364) +++ owbuild/branches/wengophone-2.2/owbuild/FindBoost.cmake 2007-08-23 09:31:59 UTC (rev 12365) @@ -8,34 +8,6 @@ # BOOST_DEFINITIONS - Compiler switches required for using Boost # BOOST_LIBRARIES_SUFFIX - Boost libraries name suffix (e.g -vc71-mt-gd-1_34, -gcc41-mt...) # -# BOOST_DATE_TIME_FOUND True if Boost Date Time was found. -# BOOST_FILESYSTEM_FOUND True if Boost Filesystem was found. -# BOOST_IOSTREAMS_FOUND True if Boost Iostream was found. -# BOOST_PRG_EXEC_MONITOR_FOUNDTrue if Boost Program Exec Monitor was found. -# BOOST_PROGRAM_OPTIONS_FOUND True if Boost Program Options was found. -# BOOST_PYTHON_FOUND True if Boost Python was found. -# BOOST_REGEX_FOUND True if Boost Regex was found. -# BOOST_SERIALIZATION_FOUND True if Boost Serialization was found. -# BOOST_SIGNALS_FOUND True if Boost Signals was found. -# BOOST_TEST_EXEC_MONITOR_FOUND True if Boost Test Exec Monitor was found. -# BOOST_THREAD-MT_FOUND True if Boost Thread was found. -# BOOST_UNIT_TEST_FRAMEWORK_FOUND True if Boost Unit Test Framework was found. -# BOOST_WSERIALIZATION_FOUND True if Boost WSerialization was found. -# -# BOOST_DATE_TIME_LIBRARY The Boost Date Time libary. -# BOOST_FILESYSTEM_LIBRARYThe Boost Filesystem libary. -# BOOST_IOSTREAMS_LIBRARY The Boost Iostream libary. -# BOOST_PRG_EXEC_MONITOR_LIBRARY The Boost Program libary. -# BOOST_PROGRAM_OPTIONS_LIBRARY The Boost Program libary. -# BOOST_PYTHON_LIBRARYThe Boost Python libary. -# BOOST_REGEX_LIBRARY The Boost Regex libary. -# BOOST_SERIALIZATION_LIBRARY The Boost Serialization libary. -# BOOST_SIGNALS_LIBRARY The Boost Signals libary. -# BOOST_TEST_EXEC_MONITOR_LIBRARY The Boost Test Exec Monitor libary. -# BOOST_THREAD_LIBRARYThe Boost Thread libary. -# BOOST_UNIT_TEST_FRAMEWORK_LIBRARY The Boost Unit Test Framework libary. -# BOOST_WSERIALIZATION_LIBRARYThe Boost WSerialization libary. -# # Copyright (c) 2006 Andreas Schneider [EMAIL PROTECTED] # Copyright (c) 2007 Wengo # @@ -170,6 +142,16 @@ ${BOOST_PATH_SUFFIX} ) + if (APPLE) +# CMake bug on Mac OS X: +# When include path has been found in a .framework, +# BOOST_INCLUDE_DIR is path_to_boost_inc_dir/boost +# where it should be path_to_boost_inc_dir. +# This code removes the trailing boost if needed. +if (NOT EXISTS ${BOOST_INCLUDE_DIR}/boost/config.hpp) + get_filename_component(BOOST_INCLUDE_DIR ${BOOST_INCLUDE_DIR} PATH) +endif (NOT EXISTS ${BOOST_INCLUDE_DIR}/boost/config.hpp) + endif (APPLE) foreach (TMP_BOOST_LIBRARIES_SUFFIX ${BOOST_LIBRARIES_SUFFIXES}) @@ -266,14 +248,10 @@ endif (NOT BOOST_SIGNALS_LIBRARY) if (NOT BOOST_TEST_EXEC_MONITOR_LIBRARY) - if (WIN32) -set (_name libboost_test_exec_monitor${TMP_BOOST_LIBRARIES_SUFFIX}) - else (WIN32) -set (_name boost_test_exec_monitor${TMP_BOOST_LIBRARIES_SUFFIX}) - endif (WIN32) find_library(BOOST_TEST_EXEC_MONITOR_LIBRARY NAMES - ${_name} + boost_test_exec_monitor${TMP_BOOST_LIBRARIES_SUFFIX} + libboost_test_exec_monitor${TMP_BOOST_LIBRARIES_SUFFIX} PATHS ${BOOST_LIBRARIES_SEARCH_DIRS} ) @@ -290,15 +268,10 @@ endif (NOT BOOST_THREAD_LIBRARY) if (NOT BOOST_UNIT_TEST_FRAMEWORK_LIBRARY) - set (_boost_unit_test_lib_name ) - if (WIN32) -set (_boost_unit_test_lib_name libboost_unit_test_framework${TMP_BOOST_LIBRARIES_SUFFIX}) - else (WIN32) -set (_boost_unit_test_lib_name boost_unit_test_framework${TMP_BOOST_LIBRARIES_SUFFIX}) - endif (WIN32) find_library(BOOST_UNIT_TEST_FRAMEWORK_LIBRARY NAMES - ${_boost_unit_test_lib_name} + boost_unit_test_framework${TMP_BOOST_LIBRARIES_SUFFIX} + libboost_unit_test_framework${TMP_BOOST_LIBRARIES_SUFFIX} PATHS
[Wengophone-devel] Wengophone shouldn't start initialization on --help
Hi, I just wanted to start wengophone in the debug directory. I know there is a resource parameter, but I can't find it out cause passing --help already tries to access the resource directory. This is stupid. Initialization is done to early. ./wengophone --help (info) 11:33:35 Wenbox::Wenbox(): Wenbox dll not loaded (debug) 11:33:35 int main(int, char**): WengoPhone started (debug) 11:33:35 virtual bool FileReader::open(): loading /home/anschneider/.wengophone/config.xml (debug) 11:33:35 virtual bool FileWriter::open(): saving to /home/anschneider/.wengophone/config.xml (debug) 11:33:35 virtual bool FileReader::open(): loading /usr/share/wengophone//config/config.xml (error) 11:33:35 bool ConfigManagerFileStorage::loadSystemConfig(): Could not open /usr/share/wengophone//config/config.xml (fatal) 11:33:35 /home/anschneider/workspace/source/projects/wengophone-2.2/libs/owutil/settings/src/Settings.cpp:163 boost::any Settings::getAny(const std::string) const: key 'config.version' does not exist wengophone: /home/anschneider/workspace/source/projects/wengophone-2.2/libs/owutil/util/src/Logger.cpp:62: void Logger::fatal(const std::string, const std::string, const std::string, const std::string): Assertion `__null fatal error' failed. Aborted -- 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] Linix: portaudio link problems
Alec leamas wrote: I'm running into problems with the current head of 2.1 when trying to build with the libportaudio option enabled. The problems are invariably unsatisfied references to the ffmpeg av* libraries. The ffmpeg API has changed. We've added support for the new API in the wengophone-2.2 branch, but we have still some problems. On 32-bit suse the problems disappears if I enable the internal ffmpeg library. If I try to use the external libraries (which are installed) I get link errors in the final link step with the unsatisfied references above. On 64-bit Fedora I get the same link error when trying to use external libraries. Trying to use the internal ffmpeg I get make[2]: *** No rule to make target `.. /libs/3rdparty/ffmpeg/libavcodec/libavcodec.a', needed by `libs/owwebcam/libowwebcam.so'. I am able to build without the portaudioption. However, no sound on Fedora ;-) So I thought I should give libportaudio a chance... Is this known bugs, is it like it's intended to be, or am I just doing something stupid? Portaudio doesn't really work, use ALSA and set the device with PH_FORCE_AUDIO_DEVICE. Search for it in the wiki. Improved audio support will be available with wengophone-2.2 too. Packages for openSUSE are available at Packman. -- andreas Any clues out there? --Alec ___ 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
[Wengophone-devel] WengoPhone has V4L2 support now
Hi List, I've committed the Video4Linux2 patches from Jarosław Lewandowski (ticket #1470) to the wengophone 2.2 branch and got my webcam running (uvcvideo). Some webcams need the framerate set after the resolution was set. If you have a webcam please test. Thanks, -- 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
Re: [Wengophone-devel] support newer ffmpeg
Minh Phan wrote: Dave, It's not absolutely necessary but is it causing problem? Initializing it by default is just easier to code. Initializing it on demand requires some extra works. I think Alban asked cause resampling isn't used in phapi. It just gets initialized and closed. -- andreas Minh -Original Message- From: [EMAIL PROTECTED] [mailto:wengophone- [EMAIL PROTECTED] On Behalf Of Dave Neary Sent: mardi 24 juillet 2007 14:01 To: [EMAIL PROTECTED] Cc: wengophone-devel@lists.openwengo.com Subject: Re: [Wengophone-devel] support newer ffmpeg Hi, Alban browaeys wrote: Remains the issue of phapi where I did not found out the rationale and th even the use of img_resample_init ... I disable the code. Could you comment, validate or commmit. Mathieu or Minh, could one of you explain why we initialise ffmpeg systematically in phapi? Is there a good reason for it? 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 ___ 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] support newer ffmpeg
Alban browaeys wrote: The api change : http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/2006-September/015181.html How it works today: http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/2006-October/016469.html [1] Thus I made the set of patches available in : http://dev.openwengo.com/trac/openwengo/trac.cgi/ticket/1741 Rational : It is based on : https://init.linpro.no/pipermail/skolelinux.no/cinelerra/2007-February/010115.html though regarding [1] I decided to take it the opposite that is : - sws_scale is only available in newer and transitional (those that have it but only as an emaulation while using old img_convert and img_resample) Thus I check if sws_scale is available and use it even if img_convert is also available. If it is not available I fail back to img_convert and img_resample. Hi Alban, I've roughly looked at your code at the weekend. I've wanted to commit the v4l2 support for pixertool and webcam, but I don't have access to these submodules atm. About the patches: I don't think you have to check for the sw_scale symbol. It should be enough to check if the library exists. if (SWSCALE_LIBRARY) set(FFMPEG_LIBRARIES ${FFMPEG_LIBRARIES} ${SWSCALE_LIBRARY} ) set(SWSCALE_FOUND TRUE) endif (SWSCALE_LIBRARY) Create a ConfigureChecks.cmake if (SWSCALE_FOUND) set(HAVE_SWSCALE 1) endif (SWSCALE_FOUND) The code looks good. I don't like the reformat of the code. This should be done in a separate patch/commit. Maybe you can attach a cleaner version. Remains the issue of phapi where I did not found out the rationale and th even the use of img_resample_init ... I disable the code. Could you comment, validate or commmit. As soon as I have compiled the new ffmpeg version and commited the v4l2 support I will test your patches. Best regards Alban Thanks for your work! Best regards, -- 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
Re: [Wengophone-devel] Wengophone 2.1.1 crashes after 12 sec.
Michael Werner wrote: Andreas Schneider schrieb: Michael Werner wrote: Using : OpenSuSE 10.2 KDE 3.5.7 release 56.1 Kernel : 2.6.18.8-0.5-default Wengophone crashes after 13 sec. .This ist the LOG . Did you use the package from Packman? http://packman.links2linux.de/ If yes, install libqt4 version 4.3 from the build service. I should set a require for the qt version. openSUSE 10.2 ships Qt 4.1.0 and Wengophone requires at least 4.1.2. So I've built the packages against the version from the build service. -- andreas Thanks. You clue solved this problem. It's a good idea to set the require for the qt version.. Why did you compiled wengo against the buildservice version? ___ 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] Wengophone 2.1.1 crashes after 12 sec.
Michael Werner wrote: Using : OpenSuSE 10.2 KDE 3.5.7 release 56.1 Kernel : 2.6.18.8-0.5-default Wengophone crashes after 13 sec. .This ist the LOG . Did you use the package from Packman? http://packman.links2linux.de/ If yes, install libqt4 version 4.3 from the build service. I should set a require for the qt version. -- andreas . (debug) 21:35:07 void PresenceHandler::connectedEventHandler(ConnectHandler, std::string): an account is connected, login=wurstsack protocol=9 (debug) 21:35:07 void PhApiIMPresence::myPresenceStatusEventHandler(PhApiWrapper, EnumPresenceState::MyPresenceStatus, const std::string): my presence status=0 (debug) 21:35:07 void PresenceHandler::changeMyAlias(const std::string, IMAccount*): changing alias for wurstsack, of protocol=9 with alias= (debug) 21:35:07 void PhApiIMPresence::myPresenceStatusEventHandler(PhApiWrapper, EnumPresenceState::MyPresenceStatus, const std::string): my presence status=0 (debug) 21:35:07 void PresenceHandler::changeMyIcon(const OWPicture, IMAccount*): changing icon for wurstsack, of protocol=9 (debug) 21:35:08 virtual void WsSoftUpdate::answerReceived(const std::string, int): WengoPhone is up-to-date Signal catched: SIGCHLD Abgebrochen . . . ___ 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] Initial committers on svn
Patrick Aljord wrote: On 7/17/07, Dave Neary [EMAIL PROTECTED] wrote: Our requirements are pretty specific: * Source control system must be cross-platform, and fast * A central canonical source for the software is essential * An easy migration path from our existing system (svn) The cross-platform requirement rules out git for the moment, the best distributed candidate is Mercurial, then perhaps Bazaar-NG. In fact the argument about whether centralised or decentralised source control is better is not appropriate. They are different, and suit different needs. Subversion fulfils its requirements very well - it is cross-platform, allows us to manage access rights for developers, provides a canonical source for the source code, and was very easy for developers to use from the start because of both windows GUI front ends like Tortoise and a very similar command syntax to cvs. The problem with centralized is that if I check WengoPhone head and modify it I can't commit it. I'm stuck with my modified version and I need to send the patch to the WP ML and wait for the wengo dev blessing to include my patch (I'm not blaming wengo devs, this is how svn work). I've you create a big feature, you have a big patch. But it is better if you have small pieces. With git you can always commit and you can test while you commit. And if it works you write a mail to the mailing list and say: Hey, I've created a nice feature you can pull it from my git repository. What you get is the work of the developer in small pieces! Every devs should be able to commit his own code to his own branch. With decentralized I can do just that. I can commit locally and then you wengo devs can pull the changes from me if you like them. You can have public repos with decentralized SCM too. Anyway, I guess it's all up to you and thanx for replying :-) Yes, git works the same way as Open Source work. You can get the source, you can modify it, you can distribute it. You distribute the source in YOUR git repository. Other people can pull your work from there. -- andreas Patrick ___ 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] 3.0 roadmap and beyond
Dave Neary wrote: Hi all, The 2.1 release is starting to make some waves, and now is the time to look forward to the next release. The big change which is already underway is the migration to the CoIP manager, the all-singing all-dancing modular architecture which Philippe and Tanguy have been working on for the past months. This change alone will justify the version number 3.0. Aside from this change, which will inevitably end up being a key part of the next release, I am looking for feedback on the features that we should be focussing on for this release cycle. Features don't necessarily mean new functionality - you might consider that we should focus on the usability of a particular part of the program, or the stability of a particular module. I don't want to put words in your mouth. Hi Dave, Features which should go into 2.1.x and 3.0: * A working phapi alsa driver! I still have to force PHAPI to use plughw with my second soundcard, mixer is forced to work on first soundcard, etc. * v4l2 webcam support, see ticket #1470 * Server-side contact list (thanks vadim) Features for 3.0: * Use system library of pidgin (libpurple) * Support for pidgin plugins (I need groupwise support) * Support for libjingle (Google Talk) * Integrate all the Codecamp work * Asterisk PBX Support * Call recording -- 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
Re: [Wengophone-devel] 3.0 roadmap and beyond
Gustavo A. Díaz wrote: Hi! Hello, Glad to see this project growing up :) As you know Dave, i been using WengoPhone since some time, and most for my Project/company. But (for me) there is a lack of how many users could join to a VideoConference or just simple voice call. Example case: i want to implement in my company a way to teach from distance to my students, so what best that using WengoPhone. The problem is that i will need more or equal to 5 students minimum, and better with 10 students on a conference call... so is where i see this lack. Simply setup an asterisk server to make conference calls. I think http://www.wengomeeting.com/ is the same but limited to 5 users. Cheers. Best regards, -- andreas 2007/5/22, Dave Neary [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]: Hi all, The 2.1 release is starting to make some waves, and now is the time to look forward to the next release. The big change which is already underway is the migration to the CoIP manager, the all-singing all-dancing modular architecture which Philippe and Tanguy have been working on for the past months. This change alone will justify the version number 3.0. Aside from this change, which will inevitably end up being a key part of the next release, I am looking for feedback on the features that we should be focussing on for this release cycle. Features don't necessarily mean new functionality - you might consider that we should focus on the usability of a particular part of the program, or the stability of a particular module. I don't want to put words in your mouth. What I do want is your ideas for things which you think should be proirities for this release cycle. I will also be looking to get people involved - if there is a pet feature that you are particularly interested in, then a patch, or even a decent spec and mock-up, will be welcome contributions. Based on the list of ideas I get from the community, and from companies working with OpenWengo, I will be publishing a first draft of a roadmap for the 3.0 release (and the release cycle beyond 3.0) during the next two weeks. Thank you very much! Cheers, Dave. -- Dave Neary OpenWengo Community Development Manager Email: [EMAIL PROTECTED] mailto:[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 mailto:Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel -- Gustavo A. Díaz GDNet Projects www.gdnet.com.ar http://www.gdnet.com.ar ___ 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] 3.0 roadmap and beyond
Helmut Pozimski wrote: Hi Dave, I tested 2.1 for some time now and there in fact a few things I'd like to see improved: *better web cam support (I still have problems with the palette settings of my web cam I didn't have with 0.99) Hi Helmut, maybe the use of v4l2 would improve it. *amd64-support (compiles but still doesn't run on amd64) It works just fine for me: /usr/bin/qtwengophone: ELF 64-bit LSB executable, AMD x86-64, version 1 (SYSV), for GNU/Linux 2.6.4, dynamically linked (uses shared libs), for GNU/Linux 2.6.4, stripped -- 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
Re: [Wengophone-devel] 2.1 feature freeze level
Vadim Lebedev wrote: I aggre, if we were using git or mercurial (which runs on windows and linux) the problem would be much easier to tackle Hi Vadim, you can use bzr with the subversion addon or svk. With this tools you can mirror a svn server, check it out locally, work on it, commit fixes to the local mirror and push them back later. They will be commited in the same small pieces to the svn server as you have them commited to your local repository. http://bazaar-vcs.org/ http://svk.bestpractical.com/ Thanks Vadim 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
Re: [Wengophone-devel] Changeset 9265
Vadim Lebedev wrote: Hello, I wonder if some trac/svn guru can explain me how i can download Changest 9265 branch/wengophone-ipv6 in *.patch file format. I want to apply this patch to my branch Go to the trac page, select the changeset, go to the bottom and select unified diff. Link: http://dev.openwengo.com/trac/openwengo/trac.cgi/changeset/9265?format=diffnew=9265 Thanks Vadim -- 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] Gaim renamed to Pidgin
Hi, Gaim has been renamed to Pidgin cause of some trouble with AOL. Pidgin should be released next week. libgaim will be renamed to libpurple. http://pidgin.im/index.php?id=177 -- 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
Re: [Wengophone-devel] H.264
Nathan Allen Stratton wrote: I am looking for someone to intergrate x264 for openwengo linux and windows. If anyone is interested please let me know how quickly it can be done and how much. You know that MPEG-LA claims to own H264 patents? Additionally, GPL may be incompatible with their nondiscriminatory access to essential AVC/H.264 patents. See http://www.mpegla.com/avc/ 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
Re: [Wengophone-devel] wengophone 2.1 - status
Andreas Schneider wrote: The sound volume of playback and capture is to low! This is a wengophone issue. The volume of my headphone is at 10% to understand the guy at the testcall I have to put it to 100%, but then all the rest extremly loud. Could we set ticket #1525 back to wengophone 2.1 and set the priority to high? -- 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
Re: [Wengophone-devel] wengophone 2.1 - status
Jerome WAGNER wrote: Hello, Hi, It seems to me that we are flirting with this objective without really doing something that we can be proud of. It seems that too many of you still have non-acceptable difficulties on this platform. So I decided to open a new development window on the 2.1 that will hopefully put an end to long standing issues under GNU/Linux. Most of Wengo developers will spend time only on that target in the next days. One of the main problems we have on Linux is sound! Portaudio has still a lot of problems with some soundcards, especially Audigy series (btw portaudio sucks ;). There is a phmedia-alsa driver. Can we improve it and use ALSA instead of portaudio? The sound volume of playback and capture is to low! This is a wengophone issue. If you change the playback volume control in wengophone, the PCM recording volume is enabled too (Audigy 2 ZS). 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
Re: [Wengophone-devel] Re: H261 Support
michel memeteau wrote: On 07/03/07, *Andreas Schneider* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: michel memeteau wrote: Hi , Any news about H361 integration in 2.1 ? Hi, can you confirm there is no ticket open for this ? it is a subject for the Google Summer of Code http://dev.openwengo.com/trac/openwengo/trac.cgi/wiki/GoogleSummerOfCode It's written H323 , not H261? Is that what you meant ? Then There is nothing about H261 right now ? openh323 supports h261 which is used in ekiga for video streaming. openh323 has also a h263 implementation which is used by wengophone. It would be great if we could replace ffmpeg with openh323 in the next working, so that we have no IP problems anymore. -- 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] Re: H261 Support
michel memeteau wrote: On 12/03/07, *Andreas Schneider* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: It's written H323 , not H261? Is that what you meant ? Then There is nothing about H261 right now ? openh323 supports h261 which is used in ekiga for video streaming. openh323 has also a h263 implementation which is used by wengophone. OK , quite weird answer , FFMPEG include H261 , and I guess H261 support with SIP is more urgent than H323 that nobody use anymore . It would be great if we could replace ffmpeg with openh323 in the next working, so that we have no IP problems anymore. I don't really see why but I'm not an expert , The patent always apply whatever the code isn't it ? H261 and H263 have no patent issues, but FFMPEG has. So most Linux distributions can't ship FFMPEG. OpenH323 implements H261 and H263 and it is available on every Linux distribution. So we should use openh323 instead of FFMPEG like Ekiga. I've looked at x264 too. MPEG-LA claims to own H264 patents. Additionally, GPL may be incompatible with their nondiscriminatory access to essential AVC/H.264 patents. http://www.mpegla.com/avc/ 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
Re: [Wengophone-devel] Announcing OpenWengo 2.1 rc1
Dave Neary wrote: Hi, It is with great pleasure that I announce that OpenWengo 2.1 rc1 is available for download at: http://download.wengo.com/releases/WengoPhone-2.1/RC1/ Hello, packages for openSUSE 10.2 are availiable at: http://packman.links2linux.org/package/Wengophone x86_64 is already available, the i586 binary will be up in some minutes. -- 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
Re: [Wengophone-devel] Re: H261 Support
michel memeteau wrote: Hi , Any news about H361 integration in 2.1 ? Hi, can you confirm there is no ticket open for this ? it is a subject for the Google Summer of Code http://dev.openwengo.com/trac/openwengo/trac.cgi/wiki/GoogleSummerOfCode -- 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
Re: [Wengophone-devel] How to build Wengophone with GTK ?
Kornikopic wrote: Hello, We are two students and we work on creating new alternative interface for Wengophone-2.1. We will work with GTK+. Can somebody help us to compile wengophone-ng with GTK (src/presentation/gtk) ? Hi guys, I have rewritten the FindGTK2.cmake module from scratch for you and created a patch for the wengophone-2.1 branch. It shows how things need to be done. The gtk presentation doesn't compile!!! You have to fix the code or rewrite it ;) Have you made any progress yet? Thank you very much. Cheers, -- andreas -- http://www.cynapses.org/ - cybernetic synapses --- /dev/null 2006-11-25 12:43:29.0 +0100 +++ libs/3rdparty/gtk2/CMakeLists.txt 2007-02-05 15:29:59.0 +0100 @@ -0,0 +1,5 @@ +if (NOT MSVC) + include(CMakeLists-unix.txt) +else (NOT MSVC) + include(CMakeLists-msvc.txt) +endif (NOT MSVC) --- /dev/null 2006-11-25 12:43:29.0 +0100 +++ libs/3rdparty/gtk2/CMakeLists-msvc.txt 2007-03-03 14:55:24.0 +0100 @@ -0,0 +1,11 @@ +ow_create_project(gtk2) + +ow_add_public_libraries( + foo +) + +ow_add_public_include_dirs( + ${CMAKE_CURRENT_SOURCE_DIR}/include +) + +ow_copy_dir(${CMAKE_CURRENT_SOURCE_DIR}/binary-lib/msvc/*.dll ${BUILD_DIR}) --- /dev/null 2006-11-25 12:43:29.0 +0100 +++ libs/3rdparty/gtk2/CMakeLists-unix.txt 2007-03-03 12:32:19.0 +0100 @@ -0,0 +1,9 @@ +if (NOT GTK2_FOUND) + find_package(GTK2 REQUIRED) +endif (NOT GTK2_FOUND) + +ow_create_project(gtk2) + +ow_use_public_libraries( + GTK2 +) Index: wengophone/src/CMakeLists.txt === --- wengophone/src/CMakeLists.txt (revision 10084) +++ wengophone/src/CMakeLists.txt (working copy) @@ -187,7 +187,7 @@ # TODO: test, xpcom, gtk? subdirs( - #presentation/gtk + presentation/gtk presentation/qt #presentation/xpcom ) --- /dev/null 2006-11-25 12:43:29.0 +0100 +++ wengophone/src/presentation/gtk/CMakeLists.txt 2007-03-03 12:39:28.0 +0100 @@ -0,0 +1,63 @@ +ow_create_executable(gtkwengophone) + +# subdirs( +# pics/emoticons +# ) + +ow_use_private_libraries( + owphone + owbuildid + gtk2 +) + +if (MSVC) + ow_use_private_libraries( + owmemorydump + ) +endif (MSVC) + +if (SIPWRAPPER_BACKEND_SIPX) + ow_add_private_definitions( + -DSIPXWRAPPER + ) + + ow_use_private_libraries( + sipxwrapper + ) +else (SIPWRAPPER_BACKEND_SIPX) +if (SIPWRAPPER_BACKEND_PHAPI) + ow_add_private_definitions( + -DPHAPIWRAPPER + ) + + ow_use_private_libraries( + owphapiwrapper + ) +else (SIPWRAPPER_BACKEND_PHAPI) +if (IMWRAPPER_BACKEND_MULTI) + ow_add_private_definitions( + -DMULTIIMWRAPPER + ) + + ow_use_private_libraries( + owmultiimwrapper + ) +endif (IMWRAPPER_BACKEND_MULTI) +endif (SIPWRAPPER_BACKEND_PHAPI) +endif (SIPWRAPPER_BACKEND_SIPX) + +ow_add_private_include_dirs( + ${CMAKE_CURRENT_BINARY_DIR} + ${CMAKE_CURRENT_SOURCE_DIR} +) + +ow_add_sources( + ../main.cpp + GtkWengoPhone.cpp + GtkWengoPhoneLogger.cpp + WidgetFactory.cpp + phoneline/GtkPhoneLine.cpp +) + +ow_create_binary(MACOSX_BUNDLE) + 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] Problematic fixes
Hi, I did a fresh compile of wengophone and checked for problematic warnings: ERROR: Program is likely not 64bit clean. ERROR: Please investigate and fix. Problematic file(s) and their linenumbers: /home/gladiac/workspace/source/projects/wengophone-2.1/wifo/phapi/phapi-old.c:1958 ERROR: Program returns random data in a function. Please fix. Problematic file(s) and their linenumbers: /home/gladiac/workspace/source/projects/wengophone-2.1/wifo/phapi/phmedia-video-control.c:184 /home/gladiac/workspace/source/projects/wengophone-2.1/wifo/phapi/phapi-old.c:3203 /home/gladiac/workspace/source/projects/wengophone-2.1/libs/sipwrapper/src/CodecList.cpp: 75, 56 /home/gladiac/workspace/source/projects/wengophone-2.1/libs/owutil/util/src/WebBrowser.cpp:105 /home/gladiac/workspace/source/projects/wengophone-2.1/libs/sipwrapper/src/EnumPhoneCallState.cpp:62 /home/gladiac/workspace/source/projects/wengophone-2.1/libs/sipwrapper/src/EnumPhoneLineState.cpp:47 /home/gladiac/workspace/source/projects/wengophone-2.1/wifo/phapi/phevents.c:538 I've opend a ticket with the patches, see: 1407 1408 1409 1410 -- 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
Re: [Wengophone-devel] Patch to disable copying files on configure
Aurélien Gâteau wrote: Aurélien Gâteau wrote: I will probably commit this soon, but it would be nice if you could tell me if it works and whether it's a good idea. For your information, I just committed it. It's in r9984. I think we could set COPY_DATA_FILES_ON_CONFIGURE=OFF by default on Linux. -- andreas Aurélien -- 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] crash when launching Qtwengophone
Mathieu Stute wrote: On Thursday 22 February 2007 23:54, Nicolas Lécureuil wrote: when i launch wengophone using my rpms, i obtain: qtwengophone: symbol lookup error: qtwengophone: undefined symbol: owplConfigEnablePIM Hi Nicolas, owplConfigEnablePIM is one of the last function added in PhApi. The usage of this function has been introduced on revision 9902. Are you up to date? Have you tried to clean your build dir (especially the wifo one) ? Do the wifo svn:external point to https://dev.openwengo.com/svn/openwengo/wifo/trunk? I've packaged revision 9932 and it works just fine. Uhm, let say it works, but not fine ;) -- andreas Regards, ___ 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
[Wengophone-devel] Re: [Wengophone-commit] r9899 - owbuild/trunk/libs-3rdparty-cmakelists
[EMAIL PROTECTED] wrote: Please, do not reply to this mailing list, use wengophone-devel instead. Author: mstute Date: 2007-02-21 11:21:41 +0100 (Wed, 21 Feb 2007) New Revision: 9899 Modified: owbuild/trunk/libs-3rdparty-cmakelists/CMakeLists.txt Log: * (void) use internal portaudio by default Why do you want to use the internal portaudio library? On Linux you should always use the system library. Normally a distribution requires to build against the system lib cause of security issues: - the system library has been tested - the system library can be updated Else you have to fix the system library and every other application which has probably the library in the internal tree. We should use the system lib for every 3rd party lib! -- 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] WengoPhone without FFMPEG
Hi, I've looked into the code and prepared a patch to compile WengoPhone without FFMPEG. http://www.cynapses.org/tmp/wengophone/ow_no_ffmpeg.diff cmake -DPHAPI_VIDEO_SUPPORT=OFF ffmpeg is needed by pixertool for pixmap conversion and in phapi. I haven't looked deeper in the phapi source code, but there it is used for h263, h264 and mpeg4. http://www.openh323.org/ http://www.videolan.org/developers/x264.html It would be great if we could replace the FFMPEG code with code that hasn't IP issues. -- 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] Re: [Wengophone-commit] r9853
Author: xdesjardins Date: 2007-02-16 18:22:42 +0100 (Fri, 16 Feb 2007) New Revision: 9853 Modified: wengophone-ng/branches/wengophone-2.1/wengophone/src/presentation/qt/CMakeLists.txt === --- wengophone-ng/branches/wengophone-2.1/wengophone/src/presentation/qt/CMakeLists.txt 2007-02-16 17:05:15 UTC (rev 9852) +++ wengophone-ng/branches/wengophone-2.1/wengophone/src/presentation/qt/CMakeLists.txt 2007-02-16 17:22:42 UTC (rev 9853) @@ -140,6 +140,7 @@ chat/QtChatEditWidget.h chat/QtChatHistoryWidget.h chat/QtWengoStyleBar.h + chat/QtChatLogViewer.h webservices/sms/QtSms.h webservices/softupdate/QtSoftUpdate.h @@ -284,7 +285,8 @@ chat/QtChatHistoryWidget.cpp chat/QtWengoStyleBar.cpp chat/QtChatUtils.cpp - + chat/QtChatLogViewer.cpp + webservices/sms/QtSms.cpp webservices/softupdate/QtSoftUpdate.cpp webservices/softupdate/QtBrowserSoftUpdate.cpp @@ -433,6 +435,7 @@ chat/UserFrame.ui chat/AvatarFrame.ui chat/AvatarWidget.ui + chat/ChatLogViewer.ui chat/chatroom/ChatRoomInviteWidget.ui chat/ChatLogViewer.ui has been added to the CMakeLists.txt, but the file hasn't been added to svn. Please fix. Thanks, -- 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] Fix Warnings-Day
Hi, we need a fix warnings-day! There are a lot of bad warnings which we should fix, some lead to real problems. Here is a nice warning: libs/imwrapper/src/IMChatSession.cpp:203: warning: comparison of unsigned expression = 0 is always true It should be announced at the webpage and we should all meet in the IRC channel and fix as much as possible. -- 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
Re: [Wengophone-devel] Wengophone no longer in Debian testing
Didier Link wrote: Hi wengonautes, Hi guys, I think your configuration isn't correctly setup because with svn version 9734 I've this lines : It works now. Something was wrong with my SIP account. Fixed by Wengo now. -- 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
Re: [Wengophone-devel] Wengophone no longer in Debian testing
Jerome WAGNER wrote: Hello, Hmm :-( That's bad news. We have to crack these problem down for once and for all. Dave do you know if the Debian blocker tickets are all listed in the 2.1 milestone ? If not, could you synch them into the 2.1 milestone with a (debian blocker) attribute in their label ? http://dev.openwengo.com/trac/openwengo/trac.cgi/ticket/999 This bug and is the main blocker for all Linux distributions. I want to provide WengoPhone packages for SUSE on Packman, but I wouldn't before this bug is fixed. I don't have time to read into the wifo code and search for the bug, but I'm I will look into it if anyone assist me. I guess it is somewhere in phapi or eXosip. Thanks, Jerome -- 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] Third party libriary updates
Hi, I don't know how often you update 3rd party libraries inside the svn tree, but we should look that we use version which are shipped with current Linux distributions. For example I can't link against the system osip2 library cause the version we use is newer than the one shipped with openSUSE. So don't switch to newser 3rd party libraries if not really nescessary. 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
Re: [Wengophone-devel] Wengophone no longer in Debian testing
Philippe BERNERY wrote: Zanfib put a comment today on Trac: it seems the problem has been fixed since the update of osip/eXosip. Anyone can confirm? Hi Philippe, no I can't at the moment. It doesn't work for me here with latest 2.1 svn, but it could be the company's firewall. I have to try it at home tonight. -- andreas -- Philippe BERNERY [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] http://dev.openwengo.org -- 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] Wengophone no longer in Debian testing
Andreas Schneider wrote: Philippe BERNERY wrote: Zanfib put a comment today on Trac: it seems the problem has been fixed since the update of osip/eXosip. Anyone can confirm? Hi Philippe, no I can't at the moment. It doesn't work for me here with latest 2.1 svn, but it could be the company's firewall. I have to try it at home tonight. I'm not able to connect to my wengo sip account with the latest wengophone 2.1 version. I've tried the precompiled i586 binary from the web page and it doesn't work too. Something is completely wrong. -- 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
Re: [Wengophone-devel] Re: little problem with .so files
Aurélien Gâteau wrote: Gianluca Sforna wrote: Are we still talking about distro packages? if so: Yes. * put libs into /usr/lib/wengophone * add a wengophone.conf file into /etc/ld.so.conf.d containing the single line: /usr/lib/wengophone * be sure to call /sbin/ldconfig after package install and removal This schema is used in Fedora, YMMV This would work, of course, but I was just wondering if there was a solution which would not involve adding files to /etc/ld.so.conf.d. Compile the qtwengophone binary with /usr/lib/wengophone as rpath? But you're free to use the complicated way described above... -- 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
Re: [Wengophone-devel] Re: little problem with .so files
Gianluca Sforna wrote: On 2/12/07, Aurélien Gâteau [EMAIL PROTECTED] wrote: Nicolas Lécureuil wrote: Hi, what is the status of fixing librairies to not have anymore .so as libs ? because you provides libs of portaudio ( for exemple) so it conflicts with portaudio-devel on linux distributions, in + the fact that there is .so files make rpm requiring -devels files. As Andreas said, for Portaudio the best solution is probably to link to the packaged version, provided it is at least v19. Since our own libs are not intended to be used by other projects (at least for now), the simplest solution would probably be to install them in /usr/lib/wengophone, but I am not use about the necessary linker options to make sure the binary gets to find them. Any idea? Are we still talking about distro packages? if so: * put libs into /usr/lib/wengophone * add a wengophone.conf file into /etc/ld.so.conf.d containing the single line: /usr/lib/wengophone * be sure to call /sbin/ldconfig after package install and removal This schema is used in Fedora, YMMV http://dev.openwengo.com/trac/openwengo/trac.cgi/changeset/9735 ... NEEDED libc.so.6 NEEDED libX11.so.6 RPATH /usr/lib64/wengophone:/usr/lib64:/opt/gnome/lib64 RUNPATH /usr/lib64/wengophone:/usr/lib64:/opt/gnome/lib64 INIT0xa0bb30 FINI0xf2a514 ... 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
Re: [Wengophone-devel] Feedback on CMake build system
Lukas Oberhuber wrote: Hi Lukas, I wanted to give some feedback on my experience of the CMake/OWBuild build system as far as using it to build wengophone 2.1 (I haven't done any editing of makefiles) on Windows XP and MSVC2005. 1) I think the speed is great! Fantastic actually. Build times have improved dramatically, and the completeness of the build is great as well (language is included automatically, there's an install target). 2) However, it is very fragile during the Makefile generation phase, the build_nmake phase. I get the feeling I can't get the same outcome twice when I run it. 2a) A couple of experience points: Finding boost appears to be a luck thing. I downloaded (r9707) which I finally got to find boost (first by copying a version of FindBoost.cmake in as per this mailing list, and then other things which I can't remember). Now it works Since then, I have downloaded (r9727) which at first I couldn't get to work (turns out I had the wrong command prompt open) - then I got the right command prompt, tried, couldn't find boost, deleted CMakeCache.txt, and still didn't work, deleted all the directories in the build directory and it still didn't work. Finally, I copied the working boost directory entries from r9707 into my CMakeCache.txt in this new directory, deleted all the sub directories, and now the build_nmake.bat and nmake work. Maybe it's just the finding of boost, maybe not. 2b) During my boost saga I realized I couldn't have boost installed just anywhere, it had to be at either c:\boost or d:\boost. Where did you install Boost? Could you send me the directory tree of your Boost installation. Could you look if there is a registry entry for the Boost path. My humble suggestion: Create a build_nmake_clean.bat, that resets everything to the beginning. That way there are no spare directories and files lying about that could confuse the situation and everyone starts from the baseline. Then, ensure that build_nmake.bat works every time from that position, and if it doesn't, that it is because something is out of place in the environment, not because there is some aspect of the CMake system in an inconsistent state. If something is out of place in the env, i.e. boost, it would be helpful for a message such as: I'm looking for boost in c:\boost and d:\boost, and I can't find it. If it's somewhere else, please set the BOOST_ROOT env variable to that location so that I can find the damn thing. That way I know what is wrong, not just that something is wrong. Please send me first the informations mentioned above. If nothing helps, I will look what we can display as error message. Btw. Windows sucks! ;) Finally, I hope this helps, and that it doesn't sound like a rant or any such thing. It's hard to do a cross platform build system right, and a little bit more fit and finish on this will go a tremendously long way! Thanks! -Lukas -- andreas Lukas Oberhuber Founder | Sipalive sip/email:[EMAIL PROTECTED] | mobile:+44 7748 638393 ___ 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: PGP signature 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] New build script for Linux
Claudio André wrote: Hi, Hi Claudio, ./build_make.sh --help Usage: build_make.sh [--configure [debug|final]|--clean|--verbose|--help] But if i try, ./build_make.sh --configure debug, i get. Unknown Option --configure. Exit The right seems to be ./build_make.sh --build debug Thanks, fixed ;) -- 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
Re: [Wengophone-devel] Is revision 9436 building on linux?
Dave Neary wrote: Hi, Philippe BERNERY wrote: Le 25 janv. 07 à 17:04, Claudio André a écrit : CMake Error: sndfile: SNDFILE_INCLUDE_DIRS and SNDFILE_INCLUDE_DIR empty, check that SNDFILE is declared before sndfile Try to install ibsndfile on your system. This is a new dependency. Hi Dave, I mentioned this to Mathieu and others earlier today on IRC - I'd like to see a mail to the mailing list systematically when the dependencies of te project change (which should ideally be very rarely) - before the change is made would be better, but a mail after the change is a minimum. It would also be cool if the docs for compiling were updated at the same time, but if they're not, at least there's some public trace of the change. Feel free to forward important commit messages to this mailing list ;) Btw. there is a changelog too, so I think there are enough channels where you can see important changes. http://dev.openwengo.com/trac/openwengo/trac.cgi/changelog Feature implement Sound for unix using libsndfile and portaudio (mstute 2007-01-24 11:16) -- andreas Cheers, Dave. -- 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] New build script for Linux
Hi, I've rewritten the build_make.sh from scratch. New Features: * Logging (build/.build.log) * Nice command line options ;) * error return values form make or cmake * build directory cleanup (--clean) more: ./build_make.sh --help Have fun, -- 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
Re: [Wengophone-devel] Wengophone 2.1 - Boost problem
Alessandro Corbelli wrote: Seems to work Thanks Bad solution, could you provide a file list of the directory so we could fix it? Thanks, -- andreas *** REPLY SEPARATOR *** On 24/01/2007 at 9.36 Jaya Meghani wrote: Same error: C:\wengocd build C:\wengo\buildset BOOST_ROOT=C:\Boost C:\wengo\buildcmake .. -DCMAKE_VERBOSE_MAKEFILE=1 -G NMake Makefiles Subversion svn command line not found, it is recommended to install it -- OS: Windows-5.1 -- Processor: x86 -- Compiler: C:/Programmi/Microsoft Visual Studio .NET 2003/Vc7/bin/cl.exe -- Build type: Debug -- Build tool: nmake -- Build directory: C:/wengo/build/debug -- svn revision: 0 CMake Error: Could not find Boost -- Configuring done Try copying C:\Program Files\CMake 2.4\share\cmake-2.4\Modules\findboost.cmake to WengoDir\cmake\Modules This should help. *** REPLY SEPARATOR *** On 24/01/2007 at 0.18 Andreas Schneider wrote: Alessandro Corbelli wrote: Hi all, Hi Alessandro, I'm having this problem when compiling wengo 2.1 C:\wengo\buildbuild_nmake.bat C:\wengo\buildcmake .. -DCMAKE_VERBOSE_MAKEFILE=1 -G NMake Makefiles Subversion svn command line not found, it is recommended to install it -- OS: Windows-5.1 -- Processor: x86 -- Compiler: C:/Programmi/Microsoft Visual Studio .NET 2003/Vc7/bin/cl.exe -- Build type: Debug -- Build tool: nmake -- Build directory: C:/wengo/build/debug -- svn revision: 0 CMake Error: Could not find Boost -- Configuring done Boost is correcty installed in C:\Boost try C:\wengo\buildset BOOST_ROOT=C:\Boost C:\wengo\buildcmake .. -DCMAKE_VERBOSE_MAKEFILE=1 -G NMake Makefiles -- andreas ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel -- http://www.cynapses.org/ - cybernetic synapses ___ 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] Wengophone 2.1 - Boost problem
Jaya Meghani wrote: Alessandro Corbelli wrote: Seems to work Thanks Bad solution, could you provide a file list of the directory so we could fix it? WengoDir\cmake\Modules\FindBoost.cmake When I use this file I get same error as reported below. But copying C:\Program Files\CMake2.4\share\cmake-2.4\Modules\findboost.cmake to WengoDir\cmake\Modules removes that error. I am using Cmake 2.4 I need a file list of C:\Boost directory to see what files are in there and what is the name of the files. -- 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
Re: [Wengophone-devel] Wengophone 2.1 - Boost problem
Alessandro Corbelli wrote: Hi all, Hi Alessandro, I'm having this problem when compiling wengo 2.1 C:\wengo\buildbuild_nmake.bat C:\wengo\buildcmake .. -DCMAKE_VERBOSE_MAKEFILE=1 -G NMake Makefiles Subversion svn command line not found, it is recommended to install it -- OS: Windows-5.1 -- Processor: x86 -- Compiler: C:/Programmi/Microsoft Visual Studio .NET 2003/Vc7/bin/cl.exe -- Build type: Debug -- Build tool: nmake -- Build directory: C:/wengo/build/debug -- svn revision: 0 CMake Error: Could not find Boost -- Configuring done Boost is correcty installed in C:\Boost try C:\wengo\buildset BOOST_ROOT=C:\Boost C:\wengo\buildcmake .. -DCMAKE_VERBOSE_MAKEFILE=1 -G NMake Makefiles -- andreas ___ 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
[Wengophone-devel] Errors to fix
Hi, I've compiled WengoPhone and generated a log file warnings (warnings.log) and one with problematic warnings (error.log). We should try to fix them asap. http://www.cynapses.org/tmp/wengophone/warnings.log http://www.cynapses.org/tmp/wengophone/error.log -- 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
Re: [Wengophone-devel] config.h problem
Didier LINK wrote: Hi all, I face to a conflict between (BUILD_DIR)/wifo/srtp/config.h[1] and wengophone-2.1/wifo/srtp/include/config.h[2] The two files were in theory generated but [1] by cmake (that I use) and [2] by scons. During the compilation, after a cmake configuration, gcc use the [2] that was not configured for a linux plateform but a windows one by default and lead to a compilation error (see tickets #1181 and #1194) due to the [1]'s masking. The revision 9169 committed by jbossart today readd [2] that mask the good one. I don't want to use scons because of the future complete switch to cmake system, so anyone can solve this conflict problem please ? This should be fixed. The config.h should be generated. Simply adding it is a more then ugly hack! -- andreas A temporary workaround is to delete [2]. Thanks for your attention. Didier Link ___ 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
[Wengophone-devel] SVN access
Hi, I have no svn access for wengophone-2.1 branch and for owbuild. I have fixes here e.g. fix for the FindBoost.cmake problems :) -- 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
Re: [Wengophone-devel] SVN access
Dave Neary wrote: Hi Andreas, Andreas Schneider wrote: I have no svn access for wengophone-2.1 branch and for owbuild. I have fixes here e.g. fix for the FindBoost.cmake problems :) While you're waiting (it might be after next week with the holidays) is there any chance you could attach the patch to the trac ticket #12T4 I just created for the problem I described on the list, please? http://www.cynapses.org/tmp/wengophone/FindBoost.diff -- andreas Cheers, Dave. -- 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] Compiling Wengo NG : config.h ?
Didier LINK wrote: Hi Le mardi 19 décembre 2006 à 18:09 +0100, Gorka Pinillos a écrit : I continue trying to compile wengo and now it reports me this error: c:\dev\trunk\wifo\srtp\include\err.h(49) : fatal error C1083: No se puede abrir el archivo incluir: 'config.h': No such file or directory scons: *** [release-symbols\wifo\sVoIP\src\crypto.obj] Error 2 scons: building terminated because of errors. What's the problem Thank you all. The problem is from the rev 8909 I think. You use scons for compilation and this changeset introduce the generation of the config.h in the srtp library by the cmake construct system. Cmake generate this file from a template with correct values for all plateform supported by openwengo. This remplace a static config.h file only suitable for Windows plateform. So if you really need scons it's a bug that you can report, if not use cmake instead. SCons will be removed from trunk soon. I don't think that the bug will be fixed, cause the static config.h was the bug :) -- andreas Regards. Didier Link ___ 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] [linux] bad REGISTER request with 64 bits system
Didier LINK wrote: Hi all, Hi Didier, If you need it, I can send to you all the wireshark records I have. Thanks for comment(s), I can also open a new ticket on trac if you want. You are looking for http://dev.openwengo.org/trac/openwengo/trac.cgi/ticket/999 :) Best regards. Didier Link -- 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
Re: [Wengophone-devel] [linux] bad REGISTER request with 64 bits system
Didier LINK wrote: Yes I know, I've write two of the comments, my pseudo is Zanfib ;) Without more comments I've tried the mailing-list, thanks to your attention ! I think the problem is maybe in the md5 digest code or something similar. Anybody have an idea how to look for a more accurate debugging ? I'm completely new in the openwengo code and I need a big picture to point in the right direction ;) It is a bug in phapi or maybe in exosip. We go only once in phAddVline2, but 2 or 3 times in phvlRegister before the first ph_reg_progress. That is not normal. We should have 1 phvlRegister followed by a ph_reg_progress. Since we go 1 time in phAddVline2 and there are no loops around phvlRegister , the additional phvlRegister can only come from ph_refresh_vlines. It would mean that ph_event_get is called too early. This would mean the ph_api_thread behaves diffently on x64_64. This was the last state we discovered. Maybe you have the time to look into it. Regards. Didier Link 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
Re: [Wengophone-devel] Avoid gcc 4.1: it makes wengophone crash!
Ludovico Cavedon wrote: Hi! Hi Ludovico, To test if your compiler is broken, you can try to compile and run this file: http://netgroup.polito.it/~cavedon/test-gcc-boost.cc this should be the correct output http://netgroup.polito.it/~cavedon/test-gcc-boost.out I have tried under Ubuntu edgy: BAD: gcc-4.1 (GCC) 4.1.2 20060928 (prerelease) (Ubuntu 4.1.1-13ubuntu5) OK: gcc-4.0 (GCC) 4.0.4 20060630 (prerelease) (Ubuntu 4.0.3-4) OK: gcc-3.4 I've compiled the code here on openSUSE 10.2 which has gcc 4.1.2. Did you report the bug to the gcc bugzilla? If yes, could you please post the bug number :) Regards, Ludovico -- 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
Re: [Wengophone-devel] Avoid gcc 4.1: it makes wengophone crash!
Ludovico Cavedon wrote: On Thu, 2006-12-14 at 09:46 +0100, Andreas Schneider wrote: I've compiled the code here on openSUSE 10.2 which has gcc 4.1.2. Did you report the bug to the gcc bugzilla? If yes, could you please post the bug number :) Did it work for you? No, it didn't. I've reported the bug for openSUSE on our bugzilla. https://bugzilla.novell.com/show_bug.cgi?id=228524 A good idea could be to ask for feedback in a gcc IRC channel. I'll try. Let us know about the results. Thanks! -- 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] HOWTO Edit Messages - Message Editing and Quoting Guide
Reading the OpenWengo mailinglist is a mess. All of you who don't know how to reply to mails on mailinglists and how to write mails to mailing lists. Please read the following HOWTO!!! http://www.guckes.net/mail/edit.html Thanks, -- 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
Re: [Wengophone-devel] idea vault and roadmap next steps
Jérôme WAGNER wrote: ## automatic drawing of library dependency ## It could be a nice thing to have a regular extract of the build system in the form of a graph of dependency of the libraries Should be no problem. All you need is the graphviz package. ## improve bug screening / ticket management ## we have had a growth in the number of ticket in the last months, but the tickets do not seem to self-organize. We have to find a way to improve the ticket screening processes And better categories, and new ones. scons is obsolete :P 2. Build system ## cmake support ## the cmake effort must go on until all platforms are totally supported under cmake I must say I'm not very happy with owbuild, it confuses me much more than it helps. But tankuy thinks it is good, so I will use it and help to develop it. ## restructuring the source tree ## the source tree has lived a lot of evolution and need a deep cleaning This should be done as soon as possible ## restructure phapi ## phapi should be splitted into its subsystem libraries and be available as an autonomous development package. It should be easy to develop and test on phapi You should rename eXosip and osip. What we have in tree isn't really eXosip it is a fork of eXosip. ## create wengophone developer bundles or devpacks ## these will greatly facilitate the entry of new developers in the community. The devpacks will allow them to download just what they need depending on what they want to work on. These devpacks could integrate precompiled binaries of some libreries But only for Windows please :) ## simplify project compile time configuration ## Generate a config.h file instead of thousand -Ddefines I will help tanguy to do that. ## monitor cpack evolution and use it ## cpack is a packaging tool that is developed in the cmake galaxy. It is not quite ready for production time but could help a lot Bill Hoffman from Kitware contacted me and offered help to get CPack and CTest working. ## Build Wengophone without FFMPEG ## it is not possible to ship WengoPhone on some distributions cause they can't ship it due the use of ffmpeg. 3. Quality assurance ## Develop on x86_64 systems ## Developing application on x86_64 system will help to make sure it works on other platforms too. ## Fix compiler warnings ## Fix warnings, which often leads too crashes or some other obscure things. ## Read the debug output of the console ## Looks like developers don't check the debugging log very often. On Linux the ALSA device list is requested about 10 times on startup. 5. Media quality ## optimize video rendering backends ## we already have code for directshow and opengl. It could be used selectively on the different platforms to optimize the rendering ## video codec plugin system in phapi, and new plugins ## theora is a must, h264 could be very interesting too. Code is already well advanced thanks to a patch from Mathias Schneider Maybe we can replace FFMPEG with theora. Use only open formats. ## automatic gain control for audio ## audio volume level (MIC and SPK) should auto-adjust to maximize/optimize the audio experience of the user Please not only auto-adjust. Make it configurable so that the user can choose what he wants :) 14. Portability ## Linux effort ## this effort will try to eradicate the last long standing issues that exist under linux ## Linux: make it ring ## under linux, the WengoPhone is not ringing when receiving an entering call Btw. why don't you use the plughw interfaces of ALSA?? The most important ALSA interfaces to the PCM devices are the plughw and the hw interface. If you use the plughw interface, you need not care much about the sound hardware. If your soundcard does not support the sample rate or sample format you specify, your data will be automatically converted. This also applies to the access type and the number of channels. With the hw interface, you have to check whether your hardware supports the configuration you would like to use. http://www.suse.de/~mana/alsa090_howto.html ## x86_64 port ## make the WengoPhone work under the x86_64 architecture It should work before the 2.0 release. 15. Bugs/Enhancements ## Linux: improve resampling ## with some audio cards under linux, resampling gets crazy and the sound is crappy. It is necessary to debug this plughw? 16. Third-party ## compile without ffmpeg ## it is necessary to have a target that allows to compile without ffmpeg Would it be possible to use only theora? -- 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
Re: [Wengophone-devel] cmake: compilation against internal portaudio if no system portaudio installed
Ludovico Cavedon wrote: On Wed, 2006-11-15 at 23:03 +0100, Andreas Schneider wrote: Ludovico Cavedon wrote: I created ticket http://dev.openwengo.com/trac/openwengo/trac.cgi/ticket/1166 - Under Linux, I noticed that building with cmake will fail if no system libportaudio is installed. However libportaudio v19 is required, which is usually not shipped with common linux distributions, because it has not been released as stable yet. I know about portaudio v0.19 shipped with openSUSE, Fedora and Debian. Ah, ok! Good! So I prefer to stick with the system library. I don't like to maintain code which I'm not responsible for. Fully agree! I thought it could be useful because portaudio is already included in wengohone source code. So, if I understand correctly, portaudio is going to be removed from openwengo tree and required as system library also with Windows and MacOS X? Afaik we don't use portaudio on MacOSX. For Windows we plan to ship a SDK with the precompiled libraries and headers. -- andreas Thank you for your answer, Reagrds, Ludovico Cavedon -- 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