Ticket #41 (closed task: invalid)

Opened 16 years ago

Last modified 16 years ago

Test all the ENABLE_* options before the release

Reported by: arnonym Assigned to: arnonym
Priority: minor Milestone: FFADO 2.0
Component: Version:
Keywords: Cc:
The device the bug applies to:

Description

Before doing the actual release (but after closing trunk for major code-changes) it has to be checked again wether compile works if only some drivers (specially _not_ the bebob) are enabled.

Change History

12/16/07 12:09:12 changed by arnonym

r760, with only bounce enabled:

g++ -o src/bounce/bounce_avdevice.os -c -O2 -DNDEBUG -DDBUS_HAS_THREADS_INIT_DEFAULT -DENABLE_BOUNCE -DENABLE_GENERICAVC -fPIC -I. -Isrc -I/home/arnold/include -I/usr/include/alsa -I/usr/include/libxml++-2.6 -I/usr/lib/libxml++-2.6/include -I/usr/include/libxml2 -I/usr/include/glibmm-2.4 -I/usr/lib/glibmm-2.4/include -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include src/bounce/bounce_avdevice.cpp
src/bounce/bounce_avdevice.cpp:52: warning: deprecated conversion from string constant to 'char*'
src/bounce/bounce_avdevice.cpp:52: warning: deprecated conversion from string constant to 'char*'
src/bounce/bounce_avdevice.cpp: In constructor 'Bounce::BounceDevice::BounceDevice(Ieee1394Service&, std::auto_ptr<ConfigRom>)':
src/bounce/bounce_avdevice.cpp:59: error: no matching function for call to 'FFADODevice::FFADODevice(Ieee1394Service&, std::auto_ptr<ConfigRom>&)'
src/ffadodevice.h:57: note: candidates are: FFADODevice::FFADODevice(DeviceManager&, std::auto_ptr<ConfigRom>)
src/ffadodevice.h:55: note:                 FFADODevice::FFADODevice(FFADODevice&)
src/ffadodevice.h: In member function 'virtual bool Bounce::BounceDevice::discover()':
src/ffadodevice.h:425: error: 'std::auto_ptr<ConfigRom> FFADODevice::m_pConfigRom' is private
src/bounce/bounce_avdevice.cpp:112: error: within this context
src/ffadodevice.h:425: error: 'std::auto_ptr<ConfigRom> FFADODevice::m_pConfigRom' is private
src/bounce/bounce_avdevice.cpp:113: error: within this context
src/bounce/bounce_avdevice.cpp: In member function 'virtual bool Bounce::BounceDevice::prepare()':
src/bounce/bounce_avdevice.cpp:286: error: 'm_p1394Service' was not declared in this scope
src/bounce/bounce_avdevice.cpp: In member function 'int Bounce::BounceDevice::allocateIsoChannel(unsigned int)':
src/bounce/bounce_avdevice.cpp:525: error: 'm_p1394Service' was not declared in this scope
src/bounce/bounce_avdevice.cpp: In member function 'bool Bounce::BounceDevice::deallocateIsoChannel(int)':
src/bounce/bounce_avdevice.cpp:535: error: 'm_p1394Service' was not declared in this scope
src/bounce/bounce_avdevice.cpp: In member function 'bool Bounce::BounceDevice::readReg(fb_nodeaddr_t, fb_quadlet_t*)':
src/bounce/bounce_avdevice.cpp:552: error: 'm_p1394Service' was not declared in this scope
src/bounce/bounce_avdevice.cpp: In member function 'bool Bounce::BounceDevice::writeReg(fb_nodeaddr_t, fb_quadlet_t)':
src/bounce/bounce_avdevice.cpp:574: error: 'm_p1394Service' was not declared in this scope
src/bounce/bounce_avdevice.cpp: In member function 'bool Bounce::BounceDevice::readRegBlock(fb_nodeaddr_t, fb_quadlet_t*, size_t)':
src/bounce/bounce_avdevice.cpp:594: error: 'm_p1394Service' was not declared in this scope
src/bounce/bounce_avdevice.cpp: In member function 'bool Bounce::BounceDevice::writeRegBlock(fb_nodeaddr_t, fb_quadlet_t*, size_t)':
src/bounce/bounce_avdevice.cpp:614: error: 'm_p1394Service' was not declared in this scope
scons: *** [src/bounce/bounce_avdevice.os] Error 1
scons: building terminated because of errors.

12/16/07 14:05:34 changed by arnonym

okay, bounce is not working. Only bebob, fireworks and motu will be supported for the release... so this is basicly nonesense...

Maybe all the ENABLE_* options are removed from the release?

02/20/08 05:19:42 changed by arnonym

  • status changed from new to closed.
  • resolution set to invalid.

superseeded by #72.

For the archive: If you use svn-trunk and one of the ENABLE_*-options is not working as expected, please report it on the ffado-devel-mailinglist or #ffado. There is no need to pollute the trac with this unless you can't reach anyone within one or two weeks...