vbcc/vasm automatic dependency files?

[phx]

Indeed. I can confirm the problem. Will notify Volker about the bug. Don't know when he will have the time for fixing, though.

[dalton]

Thanks!

Vasm dependency generation seems to work like a charm.

[phx]

Try this patch, it seemed to work for me:

--- ucpp/cpp.c  3 Mar 2016 14:17:19 -0000       1.16
+++ ucpp/cpp.c  1 Sep 2016 20:49:18 -0000       1.17
@@ -1186,7 +1186,7 @@
        if (!strcmp("time.h",fname)) misra(127,20,12,-1);
 #endif
        set_current_filename(fname);
-       handle_deps(fname,string_fname);
+       handle_deps(current_long_filename,string_fname);
        enter_file(ls, flags);
        return 0;

[dalton]

I\m glad there's a patch, but unfortunately I don't have an environment where I can compile vbcc.

For my own sake I've since long been using a Python script that recursively resolves all include statements in a c-file to generate a dependency file. It's not perfect but it does the job for me until vbcc is updated.

[phx]

Originally Posted by dalton

I\m glad there's a patch, but unfortunately I don't have an environment where I can compile vbcc.

Write me an email and tell me which vbcc-targets you need for which host platform. As long as it is something like AmigaOS, MorphOS or NetBSD I can compile it for you.

For Windows or OSX you may try to ask Leffmann.

[Leffmann]

Originally Posted by dalton

I\m glad there's a patch, but unfortunately I don't have an environment where I can compile vbcc.

I'm guessing you're using Windows. You can build the tools using the attached Visual Studio solution. It may require the Community 2015 edition (it's free), and you need to build the Release target for the x86 platform.

You can also build on the command line like this:

msbuild vbcc.sln /m /p:Configuration=Release;Platform=x86

Extract the sources to src/vbcc etc. and patch before building:
http://eab.abime.net/showpost.php?p=1073144&postcount=2

The binaries should run on Windows XP and anything later.