Balti2016 / aforge

Automatically exported from code.google.com/p/aforge
Other
0 stars 0 forks source link

Cannot build from SVN. #251

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.  Download trunk from svn.
2.  Attempt to build with VS2008.
3.  You should get 500+ compile errors.

What is the expected output? What do you see instead?
The project should build from SVN without any additional work on my behalf.

What version of the product are you using?
Trunk.

Please provide any additional information below.
The reason for this is dependencies in the project are configured incorrectly.  
For example, the "Genetic" library needs "AForge" and AForge.Math", but under 
References in VS2008 there's a warning.  Removing the bunk reference and adding 
a reference to Core and Math resolves the issue.  

Basically, the way the project is setup prevents people from cleanly building 
sources.  is there some reason the project it doing this, rather than just 
using the build-in project reference handling?

Original issue reported on code.google.com by kid...@gmail.com on 6 Sep 2011 at 1:41

GoogleCodeExporter commented 9 years ago
You just build it in the wrong way. Just select Release configuration and it 
builds fine (it is mentioned actually in Building.txt)

>> rather than just using the build-in project reference handling?
This makes it fine for Build All.sln. But it does not work when working on 
individual project, which is what used most of the time.

Original comment by andrew.k...@gmail.com on 6 Sep 2011 at 4:31

GoogleCodeExporter commented 9 years ago
>> You just build it in the wrong way.

I suppose that's one way to look at it...I don't agree--I think the project is 
configured incorrectly.  I can fix this quite easily, if you'll let me.

>> This makes it fine for Build All.sln. But it does not work when working on 
individual project, which is what used most of the time.

...this isn't true.  It will work correctly for all builds if you setup the 
references correctly.  Even if you build an individual project, if the 
references are set correctly then it'll build the required projects first.

Original comment by kid...@gmail.com on 6 Sep 2011 at 2:38

GoogleCodeExporter commented 9 years ago
>>  Even if you build an individual project, if the references are set
>> correctly then it'll build the required projects first.
Yes, but this will require adding those extra projects into the solution, which 
contains the main project we want to build. Or you know the way around it?

Original comment by andrew.k...@gmail.com on 6 Sep 2011 at 4:12

GoogleCodeExporter commented 9 years ago
>> I don't agree--I think the project is configured incorrectly. 
Also, if you select "Release", do you have issue? I suspect no. So we just need 
to resolve "Debug" build in one way or another ...

Original comment by andrew.k...@gmail.com on 6 Sep 2011 at 4:15

GoogleCodeExporter commented 9 years ago
All project/solution files are updated to use VS.NET 2010 (C#/C++ Express 
Edition 2010 is fine). Both Release and Debug builds work find out of SVN.

Committed in revisions 1635-1636. Will be released in version 2.2.3.

Original comment by andrew.k...@gmail.com on 24 Nov 2011 at 8:50

GoogleCodeExporter commented 9 years ago

Original comment by andrew.k...@gmail.com on 12 Dec 2011 at 9:16