This is really impressive work.
I gave it a try, compilation worked fine with a few hickups (mainly due
to taking some random (almost compatible) stdint.h/inttypes.h and
placing it into mago/include, so a few projects needed to have an
additional include search path).
Still, I think it is a
I attached a log for a debug session of a sample D debuggee. You can use
that as a reference for seeing where LaunchDebugTargets is supposed to end
up in the debug engine.
With respect to loading an executable as a project and having a few
problems... Were you using Windows XP? I saw those
Hi,
Here are two .bat files that help converting an entire folder
of .lib files in omf format. A subfolder omf will be created in the
current folder.
coffimplib needs to be in the current folder, too.
The batch file convert_all.bat is destined to be run in the C:
Still, I think it is a bit troublesome for people to build MaGo from
source if they are not used to work with the Visual Studio
Extensibility, so you should consider providing some precompiled
binaries.
votes++;
Hello,
Here is (attachement) a translation of file mwdebug.h
(matd.c.mwdebug).
There is a line commented out, specifically:
//extern FILE* matGetFp_d(MATFile* ph, const(char)* file, int
linenum);
since I don't know how to replace the C FILE structure.
In principle, module matd.c.mwdebug
Here is (attachement) a translation of file mwdebug.h
(matd.c.mwdebug).
Thanks for your work but unfortunately I already converted mwdebug.h in
the first place. The reason why it isn't committed yet is these functions
aren't provided by Matlab's dlls. mwdebug.cpp contains the
I don't know if there is a way to handle all this without string mixins.
i.e. something along the lines of
mixin(foo(
...
/**
* Get pointer to dimension array
*/
const(mwSize)* mxGetDimensions(const(mxArray)* pa);
...
));
and foo replaces the function defs with func(...){return
Aldo Nunez wrote:
I attached a log for a debug session of a sample D debuggee. You can use
that as a reference for seeing where LaunchDebugTargets is supposed to
end up in the debug engine.
Thanks. That helped me finding that Visual D used quotes on the
executable name. Without these, it
