I'm trying to build a cross compiler to i686-cygwin. Host is a i686
Debian 3.0 Linux with gcc 2.95.4 and glibc 2.2.5.
(Debian packages are available for mingw32 and cygwin, however the
need to access the hardware the Posix way on the target rules out
mingw and packages for cygwin appear to be un
Andrew Markebo <[EMAIL PROTECTED]> writes:
> Saw recently (yesterday?) one person posting what he did.. you should
> be able to find the article in the archive.. ahh subject "Please
> help. gcc 3.2.2 configure problem or what?"
Yes, saw it, but it deals with CVS version. I started to check it ou
I have been asked to write some code to be integrated in a legacy
Visual Basic application. This code should be available as a DLL.
I have built the i686-pc-linux -> i686-pc-cygwin cross compiler and
used it with success to compile a few small executables. Reading
mailing list archives I found
"Mader, Alexander" <[EMAIL PROTECTED]> writes:
>> - is anybody today successfully building DLLs with cygwin (not
>> mingw32) and loading them from Visual Basic (or other languages)?
>
> I have to provide DLLs for VB and do so by using Cygwin but with
> -mnocygwin, which is more or less using min
I am able to open a file and write into it from a console application,
but the same fails when done from within a function that is stored in
a DLL and called from a Visual Basic application.
This is the console app:
,
| #include
|
| int main (int argc, char * argv[]) {
| int fd;
| char
Danny Smith <[EMAIL PROTECTED]> writes:
>> I am able to open a file and write into it from a console application,
>> but the same fails when done from within a function that is stored in
>> a DLL and called from a Visual Basic application.
>
> VB expects stdcall convention.
> Try adding WINAPI to
6 matches
Mail list logo
