All MDSP binaries should be build-able with MS VS 2008

[GoogleCodeExporter]

Currently we have only one VCPROJ at that is for building funcsim. `asm` and 
`test` cannot be built using Visual Studio at all! This is not right.

The owner of this bug should perform the following steps:

1) Determine what files are used to build `asm` and `test` binaries
2) Create two new MS VS 2008 projects (they should be created as "Console 
Empty" projects, be specially careful about it!), name them asm.vcproj and 
test.vcproj, place them near funcsim.vcproj
3) Add files required for every binary to the corresponding VCPROJ.
4) Build them, make sure that they are OK.
5) Update the solution file `mdsp.sln` with two new projects.
6) Add new files to SVN

Original issue reported on code.google.com by grigory....@gmail.com on 18 Nov 2010 at 7:49

[GoogleCodeExporter]

Over to maintainer

Original comment by grigory....@gmail.com on 4 Dec 2010 at 4:08

• Changed state: Accepted

[GoogleCodeExporter]

I made my own branch and I looked for funcsim.vcproj. As I think, new 
asm.vcproj and test.vcproj should look like funcsim.vcproj.

Original comment by agilmul...@gmail.com on 5 Dec 2010 at 11:32

• Changed state: Started

[GoogleCodeExporter]

asm.vcproj is ready.

Original comment by agilmul...@gmail.com on 5 Dec 2010 at 12:05

[GoogleCodeExporter]

test.vcproj is ready.
I was faced with some problems with compilation test.vcproj. I was adding files 
from funcsim untill these problems gone.
I hope I didn't add something wrong.

Original comment by agilmul...@gmail.com on 5 Dec 2010 at 12:34

[GoogleCodeExporter]

I added new projects to mdsp.sln.

Original comment by agilmul...@gmail.com on 5 Dec 2010 at 12:50

[GoogleCodeExporter]

why don't you ask for code review?

Original comment by ikile...@gmail.com on 19 Dec 2010 at 1:19

[GoogleCodeExporter]

I'm not sure about asm.vcproj and test.vcproj quality. It still need some tests.

Original comment by agilmul...@gmail.com on 19 Dec 2010 at 1:32

• Changed state: Accepted

[GoogleCodeExporter]

For example I'm afraid I added some wrong header files to test.vcproj.

Original comment by agilmul...@gmail.com on 19 Dec 2010 at 1:36

• Changed state: Started

[GoogleCodeExporter]

Just make sure that *"Build All" *makes all the proper binaries, run them to
make sure that they work.

Original comment by grigory....@gmail.com on 19 Dec 2010 at 4:20

[GoogleCodeExporter]

Unfortunately, I made my branch before funcsim.vcproj bug was fixed. That's why 
"Build All" don't build funcsim. Should I make new branch, where this bug fixed?

Original comment by agilmul...@gmail.com on 20 Dec 2010 at 12:04

[GoogleCodeExporter]

Just update(merge) your branch to current main trunk and you'll have all the
fixes. It's obvious - you can merge not only to main trunk, but to any of
branches:

cd <folder_with_your_branch>
svn merge https://mdsp.googlecode.com/svn/trunk

Original comment by grigory....@gmail.com on 20 Dec 2010 at 6:43

[GoogleCodeExporter]

First time I used "build all" function in Visual Studio 2008, VS2008 showed me 
a error message in test.vcproj. But next time error message dissappeared!
Also asm.exe don't compile simple_test.asm. Output a.out is empty.

Original comment by agilmul...@gmail.com on 22 Dec 2010 at 10:20

[GoogleCodeExporter]

Some minutes ago I tried to compile simple_test.asm and compilation was 
completed succesfully.

Original comment by agilmul...@gmail.com on 22 Dec 2010 at 10:23

[GoogleCodeExporter]

funcsim.exe also passed the test, but before PC was showing in hex output: now 
PC is showing in decimal format. It's a bit strange.

Original comment by agilmul...@gmail.com on 22 Dec 2010 at 10:30

[GoogleCodeExporter]

Request a code review, I want to look at your magic code.

Original comment by yuri.ba...@gmail.com on 22 Dec 2010 at 10:35

[GoogleCodeExporter]

I can't commit. Tortoise showes me this message:

Commit
Commit failed (details follow):
Aborting commit: 'C:\mdsp\sources\asm\asm.vcproj' remains in conflict

I'll try to fix it.

Original comment by agilmul...@gmail.com on 22 Dec 2010 at 1:41

[GoogleCodeExporter]

You have to find the "Edit conflicts" in Tortoise menu, then make a new
version of the file in question from two variants you be faced with (it's
not so hard actually!), then find "Resolved..." and mark that file as
resolved.

After that you'll be able to commit.

Original comment by grigory....@gmail.com on 22 Dec 2010 at 2:36

[GoogleCodeExporter]

Why did Tortoise added new files to trunk? I switched Tortoise from trunk to 
branches/agilmullin.

Original comment by agilmul...@gmail.com on 22 Dec 2010 at 3:17

[GoogleCodeExporter]

Apparently you didn't noticed that you updated/switched different parts of
your code tree to different URLs. Remember that in SVN an atomic unit of
versionning is a *directory*. Different directories (possible of different
nesting layers) can be associated with different branches/tags.
*
*
If you don't specifically want such things to happen, always be sure that
you operate on the *topmost* directory (<svn_root>) and make all operations
*recursively*.
*
*
Meanwhile, you can either verify that your accidental HEAD commit does not
break anything and leave it (but please don't do that anymore) or revert it.
* *

Original comment by grigory....@gmail.com on 22 Dec 2010 at 4:58

[GoogleCodeExporter]

It's clear.
I think my commit doesn't break anything: because it just added 2 vcproj files.

Original comment by agilmul...@gmail.com on 22 Dec 2010 at 5:19

[GoogleCodeExporter]

Good. Still, your new VCPROJ'es are not added to solution file mdsp.sln . Be
sure to add them so we can build all three programs from one solution. And
be sure to make your changes available for review *in branch. *Good luck.

Original comment by grigory....@gmail.com on 22 Dec 2010 at 6:57

[GoogleCodeExporter]

Arthur, why this issue is still unfinished? It's very simple to add projects to 
solution and commit in main trunk.

Original comment by ikile...@gmail.com on 4 Apr 2011 at 8:32

[GoogleCodeExporter]

Yeah, this is the simplest issue I can imagine, but there is small pitfall in 
the solution file: you can't build without errors all files at once. I don't 
know exactly how to fix it correctly, moreover I even still don't know why does 
it happen.

Original comment by agilmul...@gmail.com on 5 Apr 2011 at 7:23

[GoogleCodeExporter]

I have an idea how to solve this.

Arthur, in VS projects' settings set up two *different *temporary folders
for two projects. E.g. Debug/funcsim/ for funcsim and Debug/asm for
assembler. This way they won't conflict when building common files.

Original comment by grigory....@gmail.com on 6 Apr 2011 at 8:24

[GoogleCodeExporter]

This idea solved the problem.

Original comment by agilmul...@gmail.com on 23 Apr 2011 at 5:47

[GoogleCodeExporter]

The changes haven't been comitted, resetting the bug.

Original comment by grigory....@gmail.com on 1 Sep 2011 at 8:42

• Changed state: New