Thanks for the info. I did manage to get a fair way with MinGW - seems
that I couldn't quite finish the job off at the linking stage at the end
:( I always like to try and use open source/free (as in speech)
software first, but I may have to succumb to the beast this time and use
VC++ :) From what I understand the Webcam stuff might not work under
MinGW anyway and we need that feature!?
Can I just say what a superb job you guys are doing with the 2.2
release! I am running it against our SIP platforms here and it is
working great so far!
By the way, is there any documentation on the sign-in procedures for
Wengo? I see you can brand the softphone and set it to login to our own
hosts which would be nice? Alternatively, it would be nice to have a
flag that turns off the Wengo style account option at startup and just
presents the SIP account settings - rather than clicking on 'Other' (for
Power users). Also, any docs/info on the SMS features and how we can
support this would be great.
I'm hoping to brand/skin our own version of Wengo for our clients to use
- but I'm happy to retain Wengo references throughout the softphone.
What are your recommendations/guidelines (keeping in mind GPL etc.) for
people who wish to brand/skin Wengo? Would you rather we remove all
Wengo references/logos or keep them in certain areas such as the 'About'
section for Copyright etc.?
Thanks again and keep up the good work!
Cheers,
Ray
Dave Neary wrote:
Hi Ray,
Ray Jackson wrote:
Okay, I managed to iron out the build problems with MinGW and Wengo and
reached the Linking stage for the WengoPhone.exe. Now I have come up
against the 'input line is too long' problem on the Windows cmd line. I
have heard reference to Perl/Python scripts, Scons etc. but can't find
any specific documentation on how I get around the command line
character limitation. Perhaps I'm not looking hard enough? Can anybody
point me in the right direction?
IIRC, Chris Brody got through all of the mingw build issues at one stage
- he's since gone quiet on the list, but he might be able to help you out.
Cheers,
Dave.
_______________________________________________
Wengophone-devel mailing list
[email protected]
http://dev.openwengo.com/mailman/listinfo/wengophone-devel