Hi Julien,
The memory allocation functions such as Xmalloc where added
in v. 2.4.0. so you probably need to upgrade to the newest
version in order to use the GreenXml library.
ciao,
D.
Hi Guy,
I had no trouble compiling/building gxml v2.3.6 as a DLL using
xsed and all of the current xblite tools.
If you are getting a linking error regarding Xmalloc, then you either
are not currently using xblite v.2.40 libraries or have some
older versions still installed.
ciao,
D.
Great job Rhett.
You are right, my link failure is not related to Julien's Xmalloc absence.
However, I had to use the new linker to successfully link gxml.obj, the older failing to link it.
Here are 2 snapshots of the same XSED screen:
1. Link ver 2_50_4048.GIF, which shows a link failure
2. Link ver 5_12_8078.GIF, with a successful link
When I see the copyright dates,
1. Link version 2.50.4048 was released in 1994
2. Link version 5.12.8078 was released in 1998, 4 years later.
It could be an issue unforeseen in 1994, but accounted for in 1998.
Bye! Guy
> Hi D.,
>
> You are right, my link failure is not related to Julien's Xmalloc absence.
> However, I had to use the new linker to successfully link gxml.obj, the older failing to link it.
Guy,
I can see no reason that gxml.x shouldn't compile as a DLL correctly using
the current linker provided by xblite. It compiles correctly on my machine.
There is no code in gxml.x that requires a newer version of link.exe. The
only reason the newer version of link may be required is if a special third
party .lib file needs to be linked.
ciao,
D.