RE: release-1-5 theme.ui needs a 'Initialize' symbol
theme.ui's completely nonfunctional just yet, so it's allowed to not work and stuff =) Isaac On 31-Aug-99 Tom Spindler wrote: > That's pretty much about it. theme.ui needs 'Initialize', or the loader > (and gdb) get cranky. >
latest cvs co missing files?
I just co on the what I think is the 1-5-branch code w/ a cvs get -r release-1-5-branch freeamp But I ran into a missing file: In file included from base/include/musicsearch.h:28, from base/include/player.h:43, from base/src/player.cpp:32: base/include/database.h:29: gdbm.h: No such file or directory Is this just me being dumb and not having gdb installed in the right place? Or is it safe to delete this reference? in the file it's included as a w/ double quotes so --timball
RE: latest cvs co missing files?
Hmm.. my bad. It's not missing files, it's missing a -I to tell it that lib/gdbm exists.. Should be fixed in cvs in 20 minutes or so, or however long it takes my poor overworked computer to do a fresh compile. Isaac On 31-Aug-99 Timothy Ball wrote: > I just co on the what I think is the 1-5-branch code w/ a >cvs get -r release-1-5-branch freeamp > > But I ran into a missing file: >In file included from base/include/musicsearch.h:28, >from base/include/player.h:43, >from base/src/player.cpp:32: >base/include/database.h:29: gdbm.h: No such file or directory > > Is this just me being dumb and not having gdb installed in the right > place? Or is it safe to delete this reference? in the file it's included > as a w/ double quotes so > > > --timball
more solaris errors.
Still building on solaris (I'm depermined to get the compile to work... If it play's then I'm just extra lucky :)) I get the error that: plm/portable/pmp300/pmp300.cpp:695: `kError_FeatureNotSupported' undeclared I've grepped areound and can't seem to find it... Anyone know what happens if I just define it as (-1)? --timball
Re: more solaris errors.
try to update again... you might have checked out in the middle of one of my check ins. elrod Timothy Ball wrote: > Still building on solaris (I'm depermined to get the compile to work... > If it play's then I'm just extra lucky :)) I get the error that: > plm/portable/pmp300/pmp300.cpp:695: `kError_FeatureNotSupported' > undeclared > I've grepped areound and can't seem to find it... Anyone know what > happens if I just define it as (-1)? > > --timball
ARG!
Last email today I swear! The solaris compile now mostly works... kinda I had to write another .h file that I called "sunDef.h" that basically has this: --snip--snip--snip-- typedef unsigned int socklen_t; #define NAME_MAX14 #define kError_FeatureNotSupported -1 --snip--snip--snip-- but it now barfs on the rio! stuff... It originally complained abt the fact that the arch stuff wasn't defined for it, so I added some lines in plm/portable/pmp300/sba/rio.cpp that looked like this: --snip--snip--snip-- #elif defined(__SRV__) #include #include #define OUTPORT( p, v ) outb( p, v ) #define INPORT( p ) inb( p ) #define CLOCK_SECONDCLOCKS_PER_SEC #define DELETARRAY delete[] --snip--snip--snip-- now when it goes to compile plm/portable/pmp300/sba/rio.cpp it complains abt parse errors LOTS of them. Can that rio stuff be turned on and off in the ./configure script? It's really *really* driving me batty. --timball
Error while compiling Freeamp 1.5 from CVS
plm/portable/pmp300/pmp300.cpp: In method `enum Error PMP300::DownloadSong(class DeviceInfo *, class PlaylistItem *, char *, bool (*)(struct PLMEvent *, void *) = 0, void * = 0)': plm/portable/pmp300/pmp300.cpp:695: `kError_FeatureNotSupported' undeclared (first use this function) plm/portable/pmp300/pmp300.cpp:695: (Each undeclared identifier is reported only once plm/portable/pmp300/pmp300.cpp:695: for each function it appears in.) make[1]: *** [plm/portable/pmp300/pmp300.o] Error 1 make[1]: Leaving directory `/usr/src/freeamp-1.5' make: *** [plugins-cc] Error 2 I commented this plugin out so I could compile, did anyone else hit this problem? -palp
Re: Error while compiling Freeamp 1.5 from CVS
this is my fault. i thought i had checked in this file, i did my checkin from too deep in the heirarchy this morning before i went to bed ... elrod Palpatine wrote: > plm/portable/pmp300/pmp300.cpp: In method `enum Error > PMP300::DownloadSong(class DeviceInfo *, class PlaylistItem *, char *, > bool (*)(struct PLMEvent *, void *) = 0, void * = 0)': > plm/portable/pmp300/pmp300.cpp:695: `kError_FeatureNotSupported' > undeclared (first use this function) > plm/portable/pmp300/pmp300.cpp:695: (Each undeclared identifier is > reported only once > plm/portable/pmp300/pmp300.cpp:695: for each function it appears in.) > make[1]: *** [plm/portable/pmp300/pmp300.o] Error 1 > make[1]: Leaving directory `/usr/src/freeamp-1.5' > make: *** [plugins-cc] Error 2 > > I commented this plugin out so I could compile, did anyone else hit this > problem? > > -palp
Re: Error while compiling Freeamp 1.5 from CVS
> >I commented this plugin out so I could compile, did anyone else hit this >problem? Try updating.. Looks like elrod just fixed it in cvs.. And just as a general note, the 1.5 branch is still semi-non functional.. Be warned =) Isaac
Re: ARG!
Reply to message from [EMAIL PROTECTED] of Tue, 31 Aug > >Last email today I swear! The solaris compile now mostly works... kinda >I had to write another .h file that I called "sunDef.h" that basically >has this: >--snip--snip--snip-- >typedef unsigned int socklen_t; >#define NAME_MAX14 >#define kError_FeatureNotSupported -1 >--snip--snip--snip-- Okey.. I'm in the process of writing configure stuff for the NAME_MAX case, and I'll add a test to see if socklen_t is defined or not.. That'll all get added to the config.h, methinks.. > >but it now barfs on the rio! stuff... It originally complained abt the >fact that the arch stuff wasn't defined for it, so I added some lines in >plm/portable/pmp300/sba/rio.cpp that looked like this: > > >now when it goes to compile plm/portable/pmp300/sba/rio.cpp it complains >abt parse errors LOTS of them. Can that rio stuff be turned on and >off in the ./configure script? It's really *really* driving me batty. Yeah, I'll futz with it.. Look for a (hopefully) working version late tonight or early tomorrow.. Isaac
Re: Error while compiling Freeamp 1.5 from CVS
i second that comment! there is a reason we have the 1.5 stuff on a branch. it is likely to break here and there for the next few weeks. when it is at a point we feel major overhauls won't be done anymore then we will merge it into the main trunk. elrod "Isaac J. Richards" wrote: > > > > >I commented this plugin out so I could compile, did anyone else hit this > >problem? > > Try updating.. Looks like elrod just fixed it in cvs.. > > And just as a general note, the 1.5 branch is still semi-non functional.. > Be warned =) > > Isaac
Re: Error while compiling Freeamp 1.5 from CVS
Those would be the error messages that I saw and was complaining abt... --timball
Freeamp 1.5
I checked out 1.5 and it seems great, before I start delving into the code, a quick question: is it ready for ui plugins to have playlist support yet? I'd like to start implementing playlist support into ncursesUI as soon as possible, so if it's ready, or the specs for how to do it when it is ready are availiable, let me know. Also: I'd like input from anyone and everyone on the look of the ncursesUI.. I've been thinking of putting in colors but I don't quite know what it should look like.. anyone with ideas, or, even better, mocked up screenshots, please, send them over.. even if you want to radically change the look, that's fine.. I'm open to anything. -palp
Re: Freeamp 1.5
the playlist manager class is very stable right now. i have been pounding on it like hell. if you find a bug let me know asap. the one thing that it does not do is communicate with the player about items being updated or added. i will add messaging in later this week after i have given it some thought. however the class should work well for adding songs and iterating them and editing playlists. there are no docs but it is fairly straightforward class to use. let me know if you have questions. elrod Palpatine wrote: > I checked out 1.5 and it seems great, before I start delving into the > code, a quick question: is it ready for ui plugins to have playlist > support yet? I'd like to start implementing playlist support into > ncursesUI as soon as possible, so if it's ready, or the specs for how to > do it when it is ready are availiable, let me know. > > Also: I'd like input from anyone and everyone on the look of the > ncursesUI.. I've been thinking of putting in colors but I don't quite know > what it should look like.. anyone with ideas, or, even better, mocked up > screenshots, please, send them over.. even if you want to radically change > the look, that's fine.. I'm open to anything. > > -palp
ncursesUI ***FREEAMP 1.5 ONLY***
This is the latest changes I made to ncursesUI, fixed to work with 1.5.. basically display fixes and some useful info on bitrate/samplerate etc on the bottom.. id3 tags aren't shown yet, once I go and look at how the playlist manager is setup I'll put that in.. hopefully by the end of the week. just untar it in freeamp/ui/ncurses. remember: this will screw up horribly with anything but 1.5. -palp ncursesUI.tar.gz
Re: ncursesUI ***FREEAMP 1.5 ONLY***
Could you please send diff's instead of the entire files? Just a request, but it's a whole lot easier on my 28.8, and I like to look at the changes. If you need help with diff, lemme know.. Ah hell, not to impinge on anyone's knowledge, here's my favorite way of doing a diff: Say you got your original freeamp/ dir that's up-to-date with current cvs, and your freeamp.working/ dir, right? so "diff -uNrd freeamp freeamp.working > freeamp.diff" would spit out a nicely formatted diff file =) Isaac At 07:30 PM 8/31/99 -0400, you wrote: > >This is the latest changes I made to ncursesUI, fixed to work with 1.5.. >basically display fixes and some useful info on bitrate/samplerate etc on >the bottom.. id3 tags aren't shown yet, once I go and look at how the >playlist manager is setup I'll put that in.. hopefully by the end of the >week. > >just untar it in freeamp/ui/ncurses. > >remember: this will screw up horribly with anything but 1.5.
Re: ncursesUI ***FREEAMP 1.5 ONLY***
Sure, I actually thought of that right *AFTER* I sent the message.. sigh. I just forgot to keep an original copy around.. Will do next time. On Tue, 31 Aug 1999, Isaac Richards wrote: > Could you please send diff's instead of the entire files? Just a request, > but it's a whole lot easier on my 28.8, and I like to look at the changes. > If you need help with diff, lemme know.. Ah hell, not to impinge on > anyone's knowledge, here's my favorite way of doing a diff: > > Say you got your original freeamp/ dir that's up-to-date with current cvs, > and your freeamp.working/ dir, right? > so "diff -uNrd freeamp freeamp.working > freeamp.diff" would spit out a > nicely formatted diff file =) > > Isaac
Re: ncursesUI ***FREEAMP 1.5 ONLY***
you can just check out a new copy and use that... elrod Palpatine wrote: > Sure, I actually thought of that right *AFTER* I sent the message.. sigh. > I just forgot to keep an original copy around.. Will do next time. > > On Tue, 31 Aug 1999, Isaac Richards wrote: > > > Could you please send diff's instead of the entire files? Just a request, > > but it's a whole lot easier on my 28.8, and I like to look at the changes. > > If you need help with diff, lemme know.. Ah hell, not to impinge on > > anyone's knowledge, here's my favorite way of doing a diff: > > > > Say you got your original freeamp/ dir that's up-to-date with current cvs, > > and your freeamp.working/ dir, right? > > so "diff -uNrd freeamp freeamp.working > freeamp.diff" would spit out a > > nicely formatted diff file =) > > > > Isaac
Re: ncursesUI ***FREEAMP 1.5 ONLY***
On Tue, 31 Aug 1999, Mark B. Elrod wrote: > you can just check out a new copy and use that... > > elrod Yeah, I know.. It's not a very good excuse, just the only one I had. -palp
