On 25-Sep-2000 Chris Kuklewicz wrote: > What is the difference between a .o and a .lo object? Nothing, really. The .lo is just an extra extension so that I can compile the few object files that are shared in the main executible and plugins with or without -fPIC as needed. Stuff in the main executible gets .o, and objects that need to be compiled again for a plugin get .lo. > Arg. I attached the short error message to this message. You forgot to initialize m_store.. Stick: HashStore *MetaData::m_store = NULL; in player.cpp or something.. Isaac _______________________________________________ [EMAIL PROTECTED] http://www.freeamp.org/mailman/listinfo/freeamp-dev
- Implementing Better String Storage Chris Kuklewicz
- RE: Implementing Better String Storage Isaac Richards
- Re: Implementing Better String Storage Chris Kuklewicz
- Re: Implementing Better String Storage Sean Ward
- Re: Implementing Better String Storage Chris Kuklewicz
- Re: Implementing Better String Storage Isaac Richards
- Re: Implementing Better String Storage Chris Kuklewicz
- Re: Implementing Better String Storage Chris Kuklewicz
- Re: Implementing Better String Storage Isaac Richards
- Re: Implementing Better String Storage Chris Kuklewicz
- Re: Implementing Better String Storage Chris Kuklewicz
- Re: Implementing Better String Storage Mark B. Elrod
- Re: Implementing Better String Storage Chris Kuklewicz