Thread: [Linux-wildo-devel] bootstrap.sh issue
Status: Pre-Alpha
Brought to you by:
darkschneider2
Menu
▾
▴
linux-wildo-devel
|
From: Benjamin P. <Ben...@ar...> - 2007-03-25 19:01:24
|
Hi darkschneider, hi all, There is a problem with the new bootstrap.sh or rather the automake (aclocal) version check. First, maybe it should exit when there was a wrong automake version. I couldn't build it on my notebook because of a wrong automake. There was a warning about an old version but the mass of automake errors made the warning hard to see. And second I now have automake 1.10 and it reports it as incorrect version since it compares the version as decimal values. Maybe we should rewrite the script to check major and minor version separately. (Same goes for aclocal) One small thing, the information about gsm.h in the INSTALL file is deprecated, isn't it? If so we should remove it or use some default configure/make/make install text. regards, Benjamin Peter |
|
From: Scorpyn . <sc...@ho...> - 2007-03-26 16:54:55
|
<html><div style='background-color:'><DIV class=RTE> <P>Hi!</P> <P>I'll only reply regarding the gsm.h issue because I'm not familiar enough with the other stuff.</P> <P>A better description of what to do with the gsm.h file can be found in INSTALL.Cygwin (section 2), maybe we could simply copy that section into the INSTALL file? It'll probably have to be rewritten slightly though. (Some stuff should probably be added aswell, like run bootstrap.sh and make sure you have gtk libs etc).</P> <P>I'll try to have a look at this tonight.<BR><BR></P></DIV> <DIV></DIV> <BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #a0c6e5 2px solid; MARGIN-RIGHT: 0px"><FONT style="FONT-SIZE: 11px; FONT-FAMILY: tahoma,sans-serif"> <HR color=#a0c6e5 SIZE=1> <DIV></DIV>From: <I>Benjamin Peter <Ben...@ar...></I><BR>Reply-To: <I>lin...@li...</I><BR>To: <I>lin...@li...</I><BR>Subject: <I>[Linux-wildo-devel] bootstrap.sh issue</I><BR>Date: <I>Sun, 25 Mar 2007 21:01:20 +0200</I><BR>MIME-Version: <I>1.0</I><BR>Received: <I>from lists-outbound.sourceforge.net ([66.35.250.225]) by bay0-mc11-f12.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2668); Sun, 25 Mar 2007 12:01:26 -0700</I><BR>Received: <I>from sc8-sf-list1-new.sourceforge.net (sc8-sf-list1-new-b.sourceforge.net [10.3.1.93])by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTPid 6C84B12032; Sun, 25 Mar 2007 11:01:26 -0800 (PST)</I><BR>Received: <I>from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]helo=mail.sourceforge.net)by sc8-sf-list1-new.sourceforge.net with esmtp (Exim 4.43)id 1HVXy0-0001Sm-Hs for lin...@li...;Sun, 25 Mar 2007 12:01:24 -0700</I><BR>Received: <I>from mail-in-01.arcor-online.net ([151.189.21.41])by mail.sourceforge.net with esmtp (Exim 4.44) id 1HVXxz-00046s-2Mfor lin...@li...;Sun, 25 Mar 2007 12:01:24 -0700</I><BR>Received: <I>from mail-in-03-z2.arcor-online.net (mail-in-03-z2.arcor-online.net[151.189.8.15])by mail-in-01.arcor-online.net (Postfix) with ESMTP id 66AB21934A8for <lin...@li...>;Sun, 25 Mar 2007 21:01:19 +0200 (CEST)</I><BR>Received: <I>from mail-in-02.arcor-online.net (mail-in-02.arcor-online.net[151.189.21.42])by mail-in-03-z2.arcor-online.net (Postfix) with ESMTP id 21CB82D366Cfor <lin...@li...>;Sun, 25 Mar 2007 21:01:19 +0200 (CEST)</I><BR>Received: <I>from [192.168.2.2] (p54a960b5.dip.t-dialin.net [84.169.96.181])(Authenticated sender: ben...@ar...)by mail-in-02.arcor-online.net (Postfix) with ESMTP id E49DA2D9A80for <lin...@li...>;Sun, 25 Mar 2007 21:01:18 +0200 (CEST)</I><BR>>Hi darkschneider, hi all,<BR>><BR>>There is a problem with the new bootstrap.sh or rather the automake<BR>>(aclocal) version check.<BR>><BR>>First, maybe it should exit when there was a wrong automake version. I<BR>>couldn't build it on my notebook because of a wrong automake. There was<BR>>a warning about an old version but the mass of automake errors made the<BR>>warning hard to see.<BR>><BR>>And second I now have automake 1.10 and it reports it as incorrect<BR>>version since it compares the version as decimal values. Maybe we should<BR>>rewrite the script to check major and minor version separately. (Same<BR>>goes for aclocal)<BR>><BR>>One small thing, the information about gsm.h in the INSTALL file is<BR>>deprecated, isn't it? If so we should remove it or use some default<BR>>configure/make/make install text.<BR>><BR>>regards,<BR>><BR>>Benjamin Peter<BR>><BR>>-------------------------------------------------------------------------<BR>>Take Surveys. Earn Cash. Influence the Future of IT<BR>>Join SourceForge.net's Techsay panel and you'll get the chance to share your<BR>>opinions on IT & business topics through brief surveys-and earn cash<BR>>http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV<BR>>_______________________________________________<BR>>Linux-wildo-devel mailing list<BR>>Lin...@li...<BR>>https://lists.sourceforge.net/lists/listinfo/linux-wildo-devel<BR></FONT></BLOCKQUOTE></div><br clear=all><hr>Express yourself instantly with MSN Messenger! <a href="http://g.msn.com/8HMBEN/2743??PS=47575" target="_top">MSN Messenger</a> Download today it's FREE!</html> |
|
From: Benjamin P. <Ben...@ar...> - 2007-03-26 17:03:07
|
Hi Scorpyn, Scorpyn . wrote: > > A better description of what to do with the gsm.h file can be found in > INSTALL.Cygwin (section 2), maybe we could simply copy that section into > the INSTALL file? It'll probably have to be rewritten slightly though. > (Some stuff should probably be added aswell, like run bootstrap.sh and > make sure you have gtk libs etc). I talked to darkschneider and the gsm.h thing is not necessary anymore the problem is solved. I don't know if anyone has tried a cygwin build lately, but I guess that file surely needs an update too. :) > > I'll try to have a look at this tonight. Sry, I just commited a 5 line version of it (before I got your mail). It is just something like a stub, if you want to make a more detailed version, please go ahead. :) regards, Benjamin Peter |
|
From: Scorpyn . <sc...@ho...> - 2007-03-27 14:43:40
|
<html><div style='background-color:'><DIV class=RTE> <P>Looks good. INSTALL.Cygwin does need to be updated aswell, because at the moment it only describes how to compile the test stuff. I think some changes to other files in the project might be necessary first though (./configure --disable-alsa comes to mind, but maybe that's already taken care of).</P> <P>I'll have a look at INSTALL.Cygwin and related stuff instead then (as I'm supposed to) :)<BR><BR></P></DIV> <DIV></DIV> <BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #a0c6e5 2px solid; MARGIN-RIGHT: 0px"><FONT style="FONT-SIZE: 11px; FONT-FAMILY: tahoma,sans-serif"> <HR color=#a0c6e5 SIZE=1> <DIV></DIV>From: <I>Benjamin Peter <Ben...@ar...></I><BR>Reply-To: <I>lin...@li...</I><BR>To: <I>lin...@li...</I><BR>Subject: <I>Re: [Linux-wildo-devel] bootstrap.sh issue</I><BR>Date: <I>Mon, 26 Mar 2007 19:03:02 +0200</I><BR>MIME-Version: <I>1.0</I><BR>Received: <I>from lists-outbound.sourceforge.net ([66.35.250.225]) by bay0-mc7-f18.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2668); Mon, 26 Mar 2007 10:03:09 -0700</I><BR>Received: <I>from sc8-sf-list1-new.sourceforge.net (sc8-sf-list1-new-b.sourceforge.net [10.3.1.93])by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTPid EFC77FD28; Mon, 26 Mar 2007 09:03:08 -0800 (PST)</I><BR>Received: <I>from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91]helo=mail.sourceforge.net)by sc8-sf-list1-new.sourceforge.net with esmtp (Exim 4.43)id 1HVsb5-0006FO-71 for lin...@li...;Mon, 26 Mar 2007 10:03:07 -0700</I><BR>Received: <I>from mail-in-09.arcor-online.net ([151.189.21.49])by mail.sourceforge.net with esmtp (Exim 4.44) id 1HVsb3-0001YF-Lufor lin...@li...;Mon, 26 Mar 2007 10:03:07 -0700</I><BR>Received: <I>from mail-in-08-z2.arcor-online.net (mail-in-08-z2.arcor-online.net[151.189.8.20])by mail-in-09.arcor-online.net (Postfix) with ESMTP id AEC8C37A474for <lin...@li...>;Mon, 26 Mar 2007 19:03:02 +0200 (CEST)</I><BR>Received: <I>from mail-in-11.arcor-online.net (mail-in-11.arcor-online.net[151.189.21.51])by mail-in-08-z2.arcor-online.net (Postfix) with ESMTP id A26662130C2for <lin...@li...>;Mon, 26 Mar 2007 19:03:02 +0200 (CEST)</I><BR>Received: <I>from [192.168.2.2] (p54A9461C.dip0.t-ipconnect.de [84.169.70.28])(Authenticated sender: ben...@ar...)by mail-in-11.arcor-online.net (Postfix) with ESMTP id 546B4281408for <lin...@li...>;Mon, 26 Mar 2007 19:03:02 +0200 (CEST)</I><BR>>Hi Scorpyn,<BR>><BR>>Scorpyn . wrote:<BR>> ><BR>> > A better description of what to do with the gsm.h file can be found in<BR>> > INSTALL.Cygwin (section 2), maybe we could simply copy that section into<BR>> > the INSTALL file? It'll probably have to be rewritten slightly though.<BR>> > (Some stuff should probably be added aswell, like run bootstrap.sh and<BR>> > make sure you have gtk libs etc).<BR>><BR>>I talked to darkschneider and the gsm.h thing is not necessary anymore<BR>>the problem is solved.<BR>><BR>>I don't know if anyone has tried a cygwin build lately, but I guess<BR>>that file surely needs an update too. :)<BR>><BR>> ><BR>> > I'll try to have a look at this tonight.<BR>><BR>>Sry, I just commited a 5 line version of it (before I got your mail). It<BR>>is just something like a stub, if you want to make a more detailed<BR>>version, please go ahead. :)<BR>><BR>><BR>>regards,<BR>><BR>>Benjamin Peter<BR>><BR>>-------------------------------------------------------------------------<BR>>Take Surveys. Earn Cash. Influence the Future of IT<BR>>Join SourceForge.net's Techsay panel and you'll get the chance to share your<BR>>opinions on IT & business topics through brief surveys-and earn cash<BR>>http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV<BR>>_______________________________________________<BR>>Linux-wildo-devel mailing list<BR>>Lin...@li...<BR>>https://lists.sourceforge.net/lists/listinfo/linux-wildo-devel<BR></FONT></BLOCKQUOTE></div><br clear=all><hr>Don't just search. Find. <a href="http://g.msn.com/8HMAEN/2749??PS=47575" target="_top">MSN Search</a> Check out the new MSN Search!</html> |
|
From: Benjamin P. <Ben...@ar...> - 2007-03-27 15:16:00
|
Hi Scorpyn, Scorpyn . wrote: > Looks good. INSTALL.Cygwin does need to be updated aswell, because at > the moment it only describes how to compile the test stuff. I think some > changes to other files in the project might be necessary first though > (./configure --disable-alsa comes to mind, but maybe that's already > taken care of). > > I'll have a look at INSTALL.Cygwin and related stuff instead then (as > I'm supposed to) :) Sounds great, please do that. --disable-alsa could be a problem at the moment since oss isn't working, but maybe darkschneider can say something about that. regards, Benjamin Peter |
|
From: Scorpyn . <sc...@ho...> - 2007-03-27 23:21:48
|
Hmm... What's the status of portaudio? Is that supported and/or still planning to be supported? The problems I've had with alsa (some or all might be fixed by now though) : 1. ./configure --disable-alsa didn't work. 2. Some of the test stuff seemed to still be using oss a while ago (linux with alsa but without oss emulation failed, but I might be assuming too much - maybe there was another issue). 3. ./configure was able to find alsa support in a Cygwin environment, but there were no header files so the compilation failed. > >Hi Scorpyn, > >Scorpyn . wrote: > > Looks good. INSTALL.Cygwin does need to be updated aswell, because at > > the moment it only describes how to compile the test stuff. I think some > > changes to other files in the project might be necessary first though > > (./configure --disable-alsa comes to mind, but maybe that's already > > taken care of). > > > > I'll have a look at INSTALL.Cygwin and related stuff instead then (as > > I'm supposed to) :) > >Sounds great, please do that. --disable-alsa could be a problem at the >moment since oss isn't working, but maybe darkschneider can say >something about that. > > >regards, > >Benjamin Peter > _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ |
|
From: Gabriele D. C. <dar...@io...> - 2007-03-28 13:39:53
|
Portaudio is code that was commited by an old developer and at that time was flagges as working. I never tested it but gros did it about 1.5 years ago and he said it was not working. The main problem is that we have sightly changed the API from that time and it probably need at least a fast lift-up (nothing complex, just a matter of naming the functions correctly and checking the are conformant to the specs). Volunter here is needed, anyone? About OSS it was working 2 weeks ago when I lastly tested it, it was working bad as OSS always did (perfect on my system thought, but not on other systems). By default the configure enable ALSA if it can find it, as many other thing it checks only for the lib and not for the headers, i have to fix all those problems cause they give issues on many system (mainly Debian!!) --disable-alsa is stupid like many other switches cause it do disable alsa but cause of the missing plugin design you still need the header to compile lw!! There is more and more worki on that configure.ac... it grows and grows, I'll have a look at what i can do, that is a bug that should be put in sf... so when someone has time he can take care of it (without forgetting it, it happens continuously). About the test stuff it would be strange it does not work when you sucessfuly compile with oss, those that does not use static instance of ALSA should still work, they are just too waiting the pluginization... then you will just choose what to use with -<something> alsa/oss/portaudio -<something> gsm/speex/CELP Regards, Gabriele Dini Ciacci On Tue, 27 Mar 2007 23:21:38 +0000 "Scorpyn ." <sc...@ho...> wrote: > Hmm... > > What's the status of portaudio? Is that supported and/or still > planning to be supported? > > The problems I've had with alsa (some or all might be fixed by now > though) : > > 1. ./configure --disable-alsa didn't work. > 2. Some of the test stuff seemed to still be using oss a while ago > (linux with alsa but without oss emulation failed, but I might be > assuming too much > - maybe there was another issue). > 3. ./configure was able to find alsa support in a Cygwin environment, > but there were no header files so the compilation failed. > > > > >Hi Scorpyn, > > > >Scorpyn . wrote: > > > Looks good. INSTALL.Cygwin does need to be updated aswell, > > > because at the moment it only describes how to compile the test > > > stuff. I think some changes to other files in the project might > > > be necessary first though (./configure --disable-alsa comes to > > > mind, but maybe that's already taken care of). > > > > > > I'll have a look at INSTALL.Cygwin and related stuff instead then > > > (as I'm supposed to) :) > > > >Sounds great, please do that. --disable-alsa could be a problem at > >the moment since oss isn't working, but maybe darkschneider can say > >something about that. > > > > > >regards, > > > >Benjamin Peter > > > > _________________________________________________________________ > Express yourself instantly with MSN Messenger! Download today it's > FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to > share your opinions on IT & business topics through brief surveys-and > earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ Linux-wildo-devel > mailing list Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linux-wildo-devel ----------- http://linux-wildo.sf.net http://www.diniciacci.org |
|
From: Scorpyn . <sc...@ho...> - 2007-03-29 09:56:52
|
<html><div style='background-color:'><DIV class=RTE> <P><FONT style="FONT-SIZE: 11px; FONT-FAMILY: tahoma,sans-serif">As far as portaudio is concerned, it's kinda on my TODO list already so I can have a look at it. I think there has been a new release of portaudio since then, so it needs to be updated to work with that aswell (I don't know if anything that affects us has changed or not though).<BR><BR>I'm not really sure what my oss problem is, but I'm guessing that its due to some errors in my kernel configuration more than anything (I had the same problem with teamspeak iirc).<BR><BR>I was hoping that fixing --disable-alsa was a simple matter of fixing the spelling error on line 203 in configure.ac, but unfortunately that doesn't seem to be the case :)</FONT><FONT style="FONT-SIZE: 11px; FONT-FAMILY: tahoma,sans-serif"><BR><BR></P></FONT> <P><FONT style="FONT-SIZE: 11px; FONT-FAMILY: tahoma,sans-serif">>Portaudio is code that was commited by an old developer and at that<BR>>time was flagges as working.<BR>>I never tested it but gros did it about 1.5 years ago and he said it<BR>>was not working.<BR>>The main problem is that we have sightly changed the<BR>>API from that time and it probably need at least a fast lift-up (nothing<BR>>complex, just a matter of naming the functions correctly and checking<BR>>the are conformant to the specs).<BR>><BR>>Volunter here is needed, anyone?<BR>><BR>>About OSS it was working 2 weeks ago when I lastly tested it, it was<BR>>working bad as OSS always did (perfect on my system thought, but not<BR>>on other systems).<BR>>By default the configure enable ALSA if it can find it, as many other<BR>>thing it checks only for the lib and not for the headers, i have to fix<BR>>all those problems cause they give issues on many system (mainly<BR>>Debian!!)<BR>>--disable-alsa is stupid like many other switches cause it do disable<BR>>alsa but cause of the missing plugin design you still need the header<BR>>to compile lw!! There is more and more worki on that configure.ac... it<BR>>grows and grows, I'll have a look at what i can do, that is a bug that<BR>>should be put in sf... so when someone has time he can take care of it<BR>>(without forgetting it, it happens continuously).<BR>><BR>>About the test stuff it would be strange it does not work when you<BR>>sucessfuly compile with oss, those that does not use static instance of<BR>>ALSA should still work, they are just too waiting the pluginization...<BR>>then you will just choose what to use with -<something><BR>>alsa/oss/portaudio -<something> gsm/speex/CELP<BR>><BR>>Regards,<BR>>Gabriele Dini Ciacci<BR>><BR>><BR>>On Tue, 27 Mar 2007 23:21:38 +0000<BR>>"Scorpyn ." <sc...@ho...> wrote:<BR>><BR>> > Hmm...<BR>> ><BR>> > What's the status of portaudio? Is that supported and/or still<BR>> > planning to be supported?<BR>> ><BR>> > The problems I've had with alsa (some or all might be fixed by now<BR>> > though) :<BR>> ><BR>> > 1. ./configure --disable-alsa didn't work.<BR>> > 2. Some of the test stuff seemed to still be using oss a while ago<BR>> > (linux with alsa but without oss emulation failed, but I might be<BR>> > assuming too much<BR>> > - maybe there was another issue).<BR>> > 3. ./configure was able to find alsa support in a Cygwin environment,<BR>> > but there were no header files so the compilation failed.<BR>> ><BR>> > ><BR>> > >Hi Scorpyn,<BR>> > ><BR>> > >Scorpyn . wrote:<BR>> > > > Looks good. INSTALL.Cygwin does need to be updated aswell,<BR>> > > > because at the moment it only describes how to compile the test<BR>> > > > stuff. I think some changes to other files in the project might<BR>> > > > be necessary first though (./configure --disable-alsa comes to<BR>> > > > mind, but maybe that's already taken care of).<BR>> > > ><BR>> > > > I'll have a look at INSTALL.Cygwin and related stuff instead then<BR>> > > > (as I'm supposed to) :)<BR>> > ><BR>> > >Sounds great, please do that. --disable-alsa could be a problem at<BR>> > >the moment since oss isn't working, but maybe darkschneider can say<BR>> > >something about that.<BR>> > ><BR>> > ><BR>> > >regards,<BR>> > ><BR>> > >Benjamin Peter<BR>> > ><BR>> ></P></FONT></DIV></div><br clear=all><hr>Express yourself instantly with MSN Messenger! <a href="http://g.msn.com/8HMBEN/2743??PS=47575" target="_top">MSN Messenger</a> Download today it's FREE!</html> |
|
From: Gabriele D. C. <dar...@io...> - 2007-03-29 11:42:38
|
Good, if you can have a look it would be nice, spec for new audio API will be out soon when me and gros can talk. We have moved to ALSA exactly cause of those OSS random errors... I am one of the luckiest linux audio user I know, everything always worked perfectly (must be cause of the live card.. that still rocks after 7-8 years :DD ) There was a typo already in the configure.ac ... probably there are more indeed, if it's on line 203 maybe it's on other lines too (you often copy and paste that code), anyway i have to add more functionality as i said to the configure script, so leave it until it's "new" On Thu, 29 Mar 2007 09:56:42 +0000 "Scorpyn ." <sc...@ho...> wrote: > As far as portaudio is concerned, it's kinda on my TODO list already > so I can have a look at it. I think there has been a new release of > portaudio since then, so it needs to be updated to work with that > aswell (I don't know if anything that affects us has changed or not > though). > > I'm not really sure what my oss problem is, but I'm guessing that its > due to some errors in my kernel configuration more than anything (I > had the same problem with teamspeak iirc). > > I was hoping that fixing --disable-alsa was a simple matter of fixing > the spelling error on line 203 in configure.ac, but unfortunately > that doesn't seem to be the case :) > > >Portaudio is code that was commited by an old developer and at that > >time was flagges as working. > >I never tested it but gros did it about 1.5 years ago and he said it > >was not working. > >The main problem is that we have sightly changed the > >API from that time and it probably need at least a fast lift-up > >(nothing complex, just a matter of naming the functions correctly > >and checking the are conformant to the specs). > > > >Volunter here is needed, anyone? > > > >About OSS it was working 2 weeks ago when I lastly tested it, it was > >working bad as OSS always did (perfect on my system thought, but not > >on other systems). > >By default the configure enable ALSA if it can find it, as many other > >thing it checks only for the lib and not for the headers, i have to > >fix all those problems cause they give issues on many system (mainly > >Debian!!) > >--disable-alsa is stupid like many other switches cause it do disable > >alsa but cause of the missing plugin design you still need the header > >to compile lw!! There is more and more worki on that configure.ac... > >it grows and grows, I'll have a look at what i can do, that is a bug > >that should be put in sf... so when someone has time he can take > >care of it (without forgetting it, it happens continuously). > > > >About the test stuff it would be strange it does not work when you > >sucessfuly compile with oss, those that does not use static instance > >of ALSA should still work, they are just too waiting the > >pluginization... then you will just choose what to use with > >-<something> alsa/oss/portaudio -<something> gsm/speex/CELP > > > >Regards, > >Gabriele Dini Ciacci > > > > > >On Tue, 27 Mar 2007 23:21:38 +0000 > >"Scorpyn ." <sc...@ho...> wrote: > > > > > Hmm... > > > > > > What's the status of portaudio? Is that supported and/or still > > > planning to be supported? > > > > > > The problems I've had with alsa (some or all might be fixed by now > > > though) : > > > > > > 1. ./configure --disable-alsa didn't work. > > > 2. Some of the test stuff seemed to still be using oss a while ago > > > (linux with alsa but without oss emulation failed, but I might be > > > assuming too much > > > - maybe there was another issue). > > > 3. ./configure was able to find alsa support in a Cygwin > > > environment, but there were no header files so the compilation > > > failed. > > > > > > > > > > >Hi Scorpyn, > > > > > > > >Scorpyn . wrote: > > > > > Looks good. INSTALL.Cygwin does need to be updated aswell, > > > > > because at the moment it only describes how to compile the > > > > > test stuff. I think some changes to other files in the > > > > > project might be necessary first though (./configure > > > > > --disable-alsa comes to mind, but maybe that's already taken > > > > > care of). > > > > > > > > > > I'll have a look at INSTALL.Cygwin and related stuff instead > > > > > then (as I'm supposed to) :) > > > > > > > >Sounds great, please do that. --disable-alsa could be a problem > > > >at the moment since oss isn't working, but maybe darkschneider > > > >can say something about that. > > > > > > > > > > > >regards, > > > > > > > >Benjamin Peter > > > > > > > > > ------------------------------------------------ > Express yourself instantly with MSN Messenger! MSN Messenger Download > today it's FREE! ----------- http://linux-wildo.sf.net http://www.diniciacci.org |
|
From: Gabriele D. C. <dar...@io...> - 2007-03-27 16:08:39
|
I did not tested the Cygwin build, when i said that gsm.h hack was not necessary anymore i was referring to the one on linux distros (cause all get the debian version of the header). Do not know which version ships with windows. Anyway windows users will not compile lw, so it's up to us to keep it in a state a developer can build the exe for windows. Regards, Gabriele Dini Ciacci On Mon, 26 Mar 2007 19:03:02 +0200 Benjamin Peter <Ben...@ar...> wrote: > Hi Scorpyn, > > Scorpyn . wrote: > > > > A better description of what to do with the gsm.h file can be found > > in INSTALL.Cygwin (section 2), maybe we could simply copy that > > section into the INSTALL file? It'll probably have to be rewritten > > slightly though. (Some stuff should probably be added aswell, like > > run bootstrap.sh and make sure you have gtk libs etc). > > I talked to darkschneider and the gsm.h thing is not necessary anymore > the problem is solved. > > I don't know if anyone has tried a cygwin build lately, but I guess > that file surely needs an update too. :) > > > > > I'll try to have a look at this tonight. > > Sry, I just commited a 5 line version of it (before I got your mail). > It is just something like a stub, if you want to make a more detailed > version, please go ahead. :) > > > regards, > > Benjamin Peter > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to > share your opinions on IT & business topics through brief surveys-and > earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ Linux-wildo-devel > mailing list Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linux-wildo-devel ----------- http://linux-wildo.sf.net http://www.diniciacci.org |
|
From: Scorpyn . <sc...@ho...> - 2007-03-27 23:10:06
|
Some people may want to compile it in a windows environment though, and libgsm is not shipped with Cygwin (unless I somehow managed to miss it). However, it's already covered in INSTALL.Cygwin (section 2) so there shouldn't be any problems related to that. > >I did not tested the Cygwin build, when i said that gsm.h hack was not >necessary anymore i was referring to the one on linux distros (cause all >get the debian version of the header). >Do not know which version ships with windows. Anyway windows users >will not compile lw, so it's up to us to keep it in a state a developer >can build the exe for windows. > >Regards, >Gabriele Dini Ciacci > >On Mon, 26 Mar 2007 19:03:02 +0200 >Benjamin Peter <Ben...@ar...> wrote: > > > Hi Scorpyn, > > > > Scorpyn . wrote: > > > > > > A better description of what to do with the gsm.h file can be found > > > in INSTALL.Cygwin (section 2), maybe we could simply copy that > > > section into the INSTALL file? It'll probably have to be rewritten > > > slightly though. (Some stuff should probably be added aswell, like > > > run bootstrap.sh and make sure you have gtk libs etc). > > > > I talked to darkschneider and the gsm.h thing is not necessary anymore > > the problem is solved. > > > > I don't know if anyone has tried a cygwin build lately, but I guess > > that file surely needs an update too. :) > > > > > > > > I'll try to have a look at this tonight. > > > > Sry, I just commited a 5 line version of it (before I got your mail). > > It is just something like a stub, if you want to make a more detailed > > version, please go ahead. :) > > > > > > regards, > > > > Benjamin Peter > > _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ |
|
From: Gabriele D. C. <dar...@io...> - 2007-03-28 13:22:28
|
I asked a bit ago and libgsm was in cygwin, maybe ehy said me wrong, anyway as you said it is covered in INSTALL.Cygwin so no problem. Yes someone will want to compile it and we have indeed to take care of them, but we hope that if they start a compile in cygwin they are somehow "experienced", we will take care of the inexperienced part later and point them to a prebuild bin meanhwile. Regards Gabriele Dini Ciacci On Tue, 27 Mar 2007 23:09:56 +0000 "Scorpyn ." <sc...@ho...> wrote: > Some people may want to compile it in a windows environment though, > and libgsm is not shipped with Cygwin (unless I somehow managed to > miss it). > > However, it's already covered in INSTALL.Cygwin (section 2) so there > shouldn't be any problems related to that. > > > > >I did not tested the Cygwin build, when i said that gsm.h hack was > >not necessary anymore i was referring to the one on linux distros > >(cause all get the debian version of the header). > >Do not know which version ships with windows. Anyway windows users > >will not compile lw, so it's up to us to keep it in a state a > >developer can build the exe for windows. > > > >Regards, > >Gabriele Dini Ciacci > > > >On Mon, 26 Mar 2007 19:03:02 +0200 > >Benjamin Peter <Ben...@ar...> wrote: > > > > > Hi Scorpyn, > > > > > > Scorpyn . wrote: > > > > > > > > A better description of what to do with the gsm.h file can be > > > > found in INSTALL.Cygwin (section 2), maybe we could simply copy > > > > that section into the INSTALL file? It'll probably have to be > > > > rewritten slightly though. (Some stuff should probably be added > > > > aswell, like run bootstrap.sh and make sure you have gtk libs > > > > etc). > > > > > > I talked to darkschneider and the gsm.h thing is not necessary > > > anymore the problem is solved. > > > > > > I don't know if anyone has tried a cygwin build lately, but I > > > guess that file surely needs an update too. :) > > > > > > > > > > > I'll try to have a look at this tonight. > > > > > > Sry, I just commited a 5 line version of it (before I got your > > > mail). It is just something like a stub, if you want to make a > > > more detailed version, please go ahead. :) > > > > > > > > > regards, > > > > > > Benjamin Peter > > > > > _________________________________________________________________ > Express yourself instantly with MSN Messenger! Download today it's > FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to > share your opinions on IT & business topics through brief surveys-and > earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ Linux-wildo-devel > mailing list Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linux-wildo-devel ----------- http://linux-wildo.sf.net http://www.diniciacci.org |
Thanks for helping keep SourceForge clean.
X