Re: [AD] Allegro 4.9.20 + MSVS 9

["Miquel 'Fire' Burns" <miquelfire@xxxxxxxxxx>]

On Thu, Apr 1, 2010 at 1:30 PM, Evert Glebbeek <eglebbk@xxxxxxxxxx> wrote:
> On 1 Apr 2010, at 11:55 , John Murphy wrote:
>> MSVS places the EXE files in a folder named after the configuration (Debug, Release, etc)
>> The demos/examples assume their data folders are at the same level as the EXE file.
>> When run from the IDE, this assumption works because the IDE reforms relative paths as if the EXE file were in the parent directory (No "Debug/Release/etc").
>
> I guess you mean that the examples look for the data in the current directory, and the IDE makes sure (by coincidence?) that this works out? I don't know what "the IDE reforms relative paths as if the EXE file were in the parent directory" means otherwise.
>
>> However, the a5steroids demo resource locater uses an absolute path so MSVS does not reform the path; it does not run inside or outside MSVS until the data files are properly located relative to the EXE file.
>
> Well, I guess the demo was written before the path interface was available, so it should probably be updated to make proper use of it. This will have to work "properly" even if the program is not "installed" as a program, though.
>
>> The examples use relative paths, so they work from inside MSVS, but they don't work when run from outside MSVS.
>
> This is a little more tricky. I don't think the examples should use the full path API (unless they're testing the path API, obviously) because that would probably just detract from the rest of the example.
>
>> I can supply patches for the above; however I don't have much experience with the Allegro dev process and git-svn. Also I can only test the MSVC platform.
>> Please tell me if you'd like my patches, and how to test/apply them to the SVN repository.
>
> Post your patches to the mainling list and one of us will (hopefully) review them and commit them for you.
>
> Evert
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> --
> https://lists.sourceforge.net/lists/listinfo/alleg-developers
>

When ran from the IDE, MSVC runs in a way like running from the main
directory, with the command being Release/program.exe, which is why
the examples work. The path API would include the Release directory.
The way things are built would require checking both data/file and
../data/file (or to remove the various output types from the end of
the path). Unless someone knows how to remove building in that path
from within CMake.

-- 
Note: No trees were killed in the sending of this message, but a large
number of electrons were terribly inconvenienced.