Yes, I can build by command line. But I also want to add some
functionalities I'm looking for. In that case I need to work on the
project and be able to edit. I didn't want to work on the head branch
as I prefer a stable version before I become familiar with it.
Should I check out the code tree by revision? How could I know which
revision number corresponds to the stable version of 1.0.3?
Many thanks for your reply!
Joshua
On Tue, Oct 14, 2008 at 2:26 AM, WangJing <wj.vivian@xxxxxxxxx> wrote:
> Yes. There is no .sln at all.
> I wonder why you must find the .sln...
>
> 2008/10/14 Tobias Wärre <tobias.warre@xxxxxxxxxxxx>
>>
>> That is because there isn't any solution file. The build is done via
>> command line, but you can build from visual studio using the nmake tools
>> also using a batch-file that calls the nmake command. That is how I solved
>> it in VS 2003 since I couldn't get it to work by using the command directly.
>> I think it depended on the location. With the batch-file I can change the
>> current directory, but I couldn't find a way to do it without the
>> batch-file. If you have the source in the project directory you can probably
>> use the command "nmake -f Makefile.nmake all" directly. (and all the others
>> that need to be executed, you have to read README.developer or the developer
>> Manual found on the Wireshark homepage.
>>
>> Regards,
>> Tobias
>>
>> -----Original Message-----
>> From: wireshark-dev-bounces@xxxxxxxxxxxxx
>> [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Joshua (Shiwei)
>> Zhao
>> Sent: den 14 oktober 2008 03:20
>> To: wireshark-dev@xxxxxxxxxxxxx
>> Subject: [Wireshark-dev] Problem on the source code of 1.0.3 version
>>
>> I downloaded the source code of 1.0.3 version since I want a stable
>> release. I can successfully build it and run.
>> However, I cannot find any solution or project file for VC++, although I
>> can see that in the source code package of latest development release.
>>
>> Is there sth wrong? I just started to look at this project and would
>> appreciate any advice you give.
>>
>> Many thanks,
>> Joshua
>> _______________________________________________
>> Wireshark-dev mailing list
>> Wireshark-dev@xxxxxxxxxxxxx
>> https://wireshark.org/mailman/listinfo/wireshark-dev
>> _______________________________________________
>> Wireshark-dev mailing list
>> Wireshark-dev@xxxxxxxxxxxxx
>> https://wireshark.org/mailman/listinfo/wireshark-dev
>
>
> _______________________________________________
> Wireshark-dev mailing list
> Wireshark-dev@xxxxxxxxxxxxx
> https://wireshark.org/mailman/listinfo/wireshark-dev
>
>
