xbox-scene.com - your xbox news information source
Quick Links: Main Forums | Xbox360 Forums | Xbox1 Forums | PS3 Forums
Xbox-Scene Forum Help  Search Xbox-Scene Forums   Xbox-Scene Forum Members   Xbox-Scene Calendar

Giganews Usenet Offers: +1150 days binary retention, 99%+ Completion, and Unlimited Speed/Access!

360 ODD Emulators: X360 Key $99 | Wasabi360 FAT $99 | Wasabi360 Slim $99
C4E's iXtreme Burner MAX Drive: LiteOn iHAS124 DROPPED TO JUST $17


Welcome Guest ( Log In | Register )

 Forum Rules Rules
 
Reply to this topicStart new topic
> Openxdk And Visual Studio 2005/2008, a workaround solution to get them to cooperate
halofreak1990
post Oct 6 2010, 09:41 PM
Post #1


X-S Young Member
*

Group: Members
Posts: 57
Joined: 6-November 08
From: The Netherlands
Member No.: 394680
Xbox Version: v1.6
360 version: v1 (xenon)



I know it's been tried before without much success to compile OpenXDK apps with VS2005.
I am a great fan of Visual Studio and its IntelliSense, and I was getting annoyed with scrolling up and down my source files to track down errors, while any program working in VS would report its compile errors and allow you to get to the faulty code with a simple double-click.

So I went searching for an answer and came up with this:
use Cygwin to compile and VS to manage the source code.

What you need is the Cygwin install recommended by OpenXDK, plus a program called 'sed', which can be found under the category 'Base' in the cygwin installer.

Once you've got Cygwin and OpenXDK working, and sed installed, open up Visual Studio and create a 'Makefile Project'
Open the properties, and go to NMake
In the 'Build Command Line' field you need to put this: make -f makefile all 2>&1 | sed -e 's/\(\w\+\):\([0-9]\+\):/\1(\2):/' where makefile is, obviously, your makefile, and 'all' is the configuration you want to build.
What this line does, is to call make, and pipe its output to sed, which then formats it in such a way VS will interpret it as if it came from msbuild. The only thing it doesn't seem to catch, are the 'no such file, or directory' errors, but if you want to see those, just go to View>Output, and take a look.

You can do the same for the 'Clean Command Line' to have VS be able to do both build, and clean:
make -f makefile clean 2>&1 | sed -e 's/\(\w\+\):\([0-9]\+\):/\1(\2):/' notice how I've replaced 'all' by 'clean'.

Now, in order to get IntelliSense to work, you need to add the paths to the OpenXDK headers to the 'Include Search Path' field, separated by ;
Also, if you want, you can define some Prepocessor definitions, but they won't be passed to make, so you should make sure that any preprocessor definitions here, are also present in your makefile.

Now, click apply, and edit away. The only non-trivial task beyond this is that you manually need to add each source file to the makefile.

This should also work in VS2008.
User is offlineProfile CardPM
Go to the top of the page
+Quote Post





Reply to this topicStart new topic

 

Lo-Fi Version Time is now: 23rd May 2013 - 06:30 AM