Hi Uma,
fine, I am happy that you are ready to work!
One place in code to start is here:
http://bazaar.launchpad.net/~mixxxdevelopers/mixxx/trunk/view/head:/mixxx/src/soundsourcemp3.cpp#L558
int SoundSourceMp3::parseHeader()
Or at any other SoundSource??::parseHeader() function.
I don't know if it possible to create an erroneous file with GHex or
similar.
If you do not have such a file, you may always return false from
parseHeader() and see if this issues the bug.
The library scanner itself is living here:
http://bazaar.launchpad.net/~mixxxdevelopers/mixxx/trunk/view/head:/mixxx/src/library/libraryscanner.cpp
Are you able to single step though the code using gdb?
When starting coding form Mixxx the Eclipse call tree function was very
valuable!
Kind regards,
Daniel
2013/3/12 Uma Priyadarsi <[email protected]>
> Hello
>
> I successfully built mixxx on linux.. and it is working smooth, as far as
> I have used it. Thank you Sean M. Pappalardo (D.J Pegasus).
>
> This bug caught my attention:
> bug#1000784<https://bugs.launchpad.net/mixxx/+bug/1000784>
> . I would like to work on it. I would like some direction on where to
> proceed from here. I mean, I would like to know how I can try to attend or
> tackle this bug, as in, where in the source code is the bug present. I
> wrote about this(this meaning: I see a bug,but then, I don't know where to
> proceed from there) in a previous mail too. And I was told, I was talking
> about bug trackers.
> But later on, I put that on back burner, and tried building mixxx on my
> system(Initially, I tried compiling mixxx on windows, and it proved to be a
> herculean task, so I shifted to linux, as suggested by Sean). Now that I
> have finished it, I would like to get back to my original goal: start by
> solving easy bugs, so that I get familiar and accustomed to the code by the
> time of gsoc.
>
> So, any help or tips on how I should proceed would be much appreciated. If
> past experience is any indicator, I have always found the replies from the
> mailing lists to be very helpful. Thank you.
>
> Cheers
> Priyadarsi
>
>
> On Sat, Mar 9, 2013 at 12:25 PM, Sean M. Pappalardo - D.J. Pegasus <
> [email protected]> wrote:
>
>> Hello.
>>
>>
>> On 03/08/2013 11:00 PM, Uma Priyadarsi wrote:
>>
>>> In step 5, part c, we have to type in the follwing command in Windows
>>> SDK command prompt:
>>>
>>> scons toolchain=msvs winlib=path_to_mixxx-win32lib-**
>>> msvc90-release_directory
>>>
>>
>> You need to replace 'path_to_mixxx-win32lib-**msvc90-release_directory'
>> with the actual path of where you downloaded the pre-compiled dependencies.
>> Which version of Visual C++ do you have and which dependency branch did you
>> download? The version used to build the dependencies must match the version
>> you build Mixxx with. MSVC 9.0 is VS 2008. I just uploaded a new branch for
>> VS 2010/MSVC 10.0: https://code.launchpad.net/~**
>> mixxxdevelopers/mixxx/winlib-**msvc10-x86-static<https://code.launchpad.net/~mixxxdevelopers/mixxx/winlib-msvc10-x86-static>
>> If you use this one, you must build with the flag staticlibs=1.
>>
>>
>> 1) "When mixxx is done compiling...". Where should I compile mixxx? Or
>>> is step 5 the process compiling mixxx?
>>>
>>
>> Yes. We use the terms 'building' and 'compiling' interchangeably, though
>> strictly speaking, 'compiling' is making the Mixxx binary itself, where
>> 'building' also includes the other things that happen, like copying DLLs
>> and the binary to the dist32 directory.
>>
>>
>> 2) I could not find both of the follwing: the directory mixxx/dist32
>>> and so obviously didnot find mixxx.exe. Does it mean I have not got the
>>> source code properly??
>>>
>>
>> No, that directory will get created as part of the build process, after
>> the dependency check succeeds.
>>
>>
>> And also, I'm spending a lot of time just trying to build mixxx.
>>>
>>
>> Unfortunately that's the reality on Windows. It's very particular about
>> the compiler version and flags used and takes a good amount of work to get
>> right. (When I first started setting up my build environment, it took over
>> a week to get Mixxx building completely due to much trial and error.) The
>> Windows build instructions on the wiki are written for those who already
>> understand how to build software on Windows, otherwise the page would be
>> much, much longer.
>>
>> I'm thinking about rewriting the wiki page to include setting up a build
>> environment, but even with that information, so many things can be
>> different on different systems (and so many things can go wrong) that it
>> still won't answer every possible concern.
>>
>> In short, if you're new to building software, doing it on Linux is far,
>> far easier. Once you decide to try on Windows, you're signing up for some
>> pain. :)
>>
>> Sincerely,
>> Sean M. Pappalardo
>> "D.J. Pegasus"
>> Mixxx Developer - Controller Specialist, Windows package maintainer
>>
>>
>
>
> ------------------------------------------------------------------------------
> Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
> Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
> endpoint security space. For insight on selecting the right partner to
> tackle endpoint security challenges, access the full report.
> http://p.sf.net/sfu/symantec-dev2dev
> _______________________________________________
> Get Mixxx, the #1 Free MP3 DJ Mixing software Today
> http://mixxx.org
>
>
> Mixxx-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mixxx-devel
>
------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
endpoint security space. For insight on selecting the right partner to
tackle endpoint security challenges, access the full report.
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org
Mixxx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mixxx-devel
