Using virtualjaguar for development

[42bs]

A dumb question maybe, but should it be possible to run .ABS files in vj? Or any other "non-ROM" format?

[JagChris]

I think @Chilly Willy hacked his to run whatever

[Sporadic]

In Windows you can just drag an abs file over VJ and it'll run. Or you can start VJ via command line and run the .abs

I can't remember the command line off hand but JagStudio does it, for example.

 

No special VJ required.

 

 

 

 

 

[42bs]

Hmm, tried it, but it does not work.

[42bs]

Meanwhile, I build a j64 file as workaround.

[Sporadic]

So in the JagStudio batch file, we use this;

 

start virtualjaguar %BUILDPATH%\%PROJECTNAME%.abs --alpine

 

Which starts VJ and auto loads the .abs . --alpine gives some of the extra Dev options

[42bs]

9 hours ago, Sporadic said:

So in the JagStudio batch file, we use this;

 

start virtualjaguar %BUILDPATH%\%PROJECTNAME%.abs --alpine

 

Which starts VJ and auto loads the .abs . --alpine gives some of the extra Dev options

I checked JagStudio. Even though it adds ".abs" it is a .COF file.

When I change my "rln" option from "-n" to "-e" VJ loads it.

Thx.

 

[Chilly Willy]

On 2/19/2022 at 3:29 PM, JagChris said:

I think @Chilly Willy hacked his to run whatever

I use the current VJ Rx from github. It has support for debug info in the form of dwarf entries when you use elf format.

 

[42bs]

4 hours ago, Chilly Willy said:

I use the current VJ Rx from github. It has support for debug info in the form of dwarf entries when you use elf format.

 

I used also. I have also cloned it, but the pity is, there is no description of the prerequisites needed. So building stopped. So I can't improve/fix it.

I will try building a ELF file.

Edited February 21, 2022 by 42bs

[42bs]

Wow: ELF worked. Nice!

[dilinger]

1 hour ago, 42bs said:

I used also. I have also cloned it, but the pity is, there is no description of the prerequisites needed. So building stopped. So I can't improve/fix it.

I will try building a ELF file.

Have you look at the Wiki pages?

[42bs]

Ouch, did fork the wrong repo which has no Wiki.

Thanks for pointing out. Will start reading ?

[Chilly Willy]

I generally look at the error message when the compile fails to see what is needed to add. For example, if it says something like it couldn't find sdl2gfx.h, you know you need to add the dev package for sdl2gfx. It usually fairly clear what was missing, and if it isn't, a quick google usually turns up which package has the missing thing in question.

 

Often, you can do a make distclean and then rerun configure. Configure will nearly always tell you when required packages are missing. But yes, dependencies for compiling SHOULD be in the readme or the wiki or wherever the build instructions are.