similar to: os/2 support using Watcom

Displaying 20 results from an estimated 600 matches similar to: "os/2 support using Watcom"

2017 Jan 23
4
os/2 support using Watcom
On 01/22/17 02:00 PM, Ozkan Sezer wrote: > Question: Does emx support __declspec(dllexport) so I can adjust > these changes? Because the emx build of the dll seems to have > exported_everything_ :( GCC supports __declspec(dllexport) though it still needs a def file, with no exports. Libtool doesn't currently and as flac uses libtool... Dave
2017 Jan 23
1
os/2 support using Watcom
On 01/23/17 01:01 AM, Erik de Castro Lopo wrote: > Dave Yeo wrote: > >> >GCC supports __declspec(dllexport) though it still needs a def file, >> >with no exports. Libtool doesn't currently and as flac uses libtool... > So you're happy with this patch? > > http://lists.xiph.org/pipermail/flac-dev/2017-January/006170.html > No. Lots of errors such
2017 Jan 22
0
os/2 support using Watcom
On 1/22/17, Dave Yeo <dave.r.yeo at gmail.com> wrote: > On 01/22/17 09:57 AM, Ozkan Sezer wrote: >> On 1/22/17, Dave Yeo <dave.r.yeo at gmail.com> wrote: >>> On 01/22/17 05:35 AM, Ozkan Sezer wrote: >>>> The attached set of patches adds support for OS/2 using Watcom compiler >>>> (tested with Open Watcom 1.9). My only interest was building a
2017 Jan 22
0
os/2 support using Watcom
On 01/22/17 05:35 AM, Ozkan Sezer wrote: > The attached set of patches adds support for OS/2 using Watcom compiler > (tested with Open Watcom 1.9). My only interest was building a working > dll (the last patch in the set adds a makefile for it), therefore I did > not touch other places: If there is interest, I can do so. Most of the patches can have s/__EMX__/__OS2__/ excepting the
2000 Dec 15
2
Ports
On Thu, 14 Dec 2000 10:06:39 +1100, Michael Smith wrote: >>I've done a port for OS/2 using Watcom C++, including a simple command line >>player based on vorbisfile_example.c, which can be downloaded from >>http://silk.apana.org.au/utils.html >>It'd be nice if my changes could be commited to CVS, should I just post >>patches here? > >Yes, unless
2014 May 24
2
make dllimport/dllexport attributes work with mingw (and others)
The following patch changes export.h so that the dllimport/dllexport attributes work with mingw/mingw-w64 and others: - changes _declspec keyword to __declspec: the former may not be defined by some toolchains. - changes the _MSC_VER condition to universally _WIN32: MSVC, as well as GCC supports this. Attached patch: declspec.diff Regards. -- O.S. -------------- next part --------------
2012 Feb 07
2
[PATCH] Remove even more CPP hackery
This commit will break OS/2's EMX 0.9d library (GCC 2.8.1) which has been been replaced by klibc. Considering the age of EMX and lack of testing and that klibc contains so many improvements I think this is exceptable. --- include/FLAC/ordinals.h | 17 +++++++++-------- src/flac/main.c | 2 +- src/libFLAC/metadata_iterators.c | 2 +-
2017 Jan 23
1
os/2 support using Watcom
Ozkan Sezer wrote: > Anyways, with the changed exports.h patch, every need should > be met now.. Sorry, which patch is that? Erik -- ---------------------------------------------------------------------- Erik de Castro Lopo http://www.mega-nerd.com/
2000 Sep 10
2
Vorbis on OS/2
Following a few months of lurking on the list, and vainly trying to get vorbis to compile on os/2, I finally managed to get the nightly gzip from saturday to compile (fairly) cleanly, and so have finally been able to play with Vorbis on my OS of choice :) Using the EMX runtime system, and bash for OS/2 (along with a few ported GNU apps), both configure and make work fine (except for ogg123
2012 Feb 07
5
[PATCH] Remove even more CPP hackery
On 02/07/12 12:03 am, Erik de Castro Lopo wrote: > Dave Yeo wrote: > >> This commit will break OS/2's EMX 0.9d library (GCC 2.8.1) which has been >> been replaced by klibc. Considering the age of EMX and lack of testing >> and that klibc contains so many improvements I think this is exceptable. > > Sorry Dave, I can't do that. Or rather sorry, the patch
2003 Oct 21
2
WATCOM compiled libraries
Hello, as usual for me with precompiled libraries, the ones of the vorbis- sdk didn't work for me in WATCOM/Win32, so i compiled them on my own (vorbis_static.lib / vorbisfile_static.lib - it was possible after some slight changes like slightly modifiyng the typedef types that Watcom didn't know) The libraries work fine so far (like getting the file info), but when calling ov_read
2000 Aug 22
1
External call to Watcom F77 version 11
A colleague is using Watcom F77 version 11 in Windows NT, and wants to create DLLs callable from R. (He was previously able to do external calls from S-PLUS). Does anyone know what magic is necessary so that it uses the right calling convention? In a debugger, it appears it's using a register-based calling convention, no matter what we ask for, but we're probably asking in the wrong
2014 May 24
2
make dllimport/dllexport attributes work with mingw (and others)
On 5/24/14, lvqcl <lvqcl.mail at gmail.com> wrote: > Ozkan Sezer <sezeroz at gmail.com> ?????(?) ? ????? ?????? Sat, 24 May 2014 > 10:16:15 +0400: > >> - changes the _MSC_VER condition to universally _WIN32: MSVC, as well >> as GCC supports this. > > MSYS/MinGW 4.8.3, 4.9.0 can't compile code from git after this patch: > > format.c:47:22: error:
2007 Feb 02
1
dynamic loading error with Open Watcom object file
Hello. I am trying to use a FORTRAN subroutine from within R (Windows version). This fortran subroutine is compiled using the Open Watcom Fortran compiler and the compiled object file is called ritscale.obj. Following the explanation on pages 193-194 of "The New S language" I use the dyn.load command: > dyn.load("f:/maxent/ritscale.obj") Error in dyn.load(x,
2005 Jan 18
1
lme confusion
Hi, this is my first time using the nlme package, and I ran into the following puzzling problem. I estimated a mixed effects model using lme, once using groupedData, once explicitly stating the equations. I had the following outputs. All the coefficients were similar, but they're always slightly different, making me think that it's not due to numerical error. Also, what is the
2012 Mar 25
2
Trying to link against libFLAC_static.lib (windows)
On Fri, Mar 23, 2012 at 9:45 PM, JonY <jon_y at users.sourceforge.net> wrote: > On 3/23/2012 13:59, Glenn McCord wrote: >> Hi. I'm trying to get a project linking to libFLAC_static.lib but I >> get linker errors such as the following. >> >> The __imp__ prefix seems to imply that some kind of .dll usage is >> happening, which it shouldn't. >>
2012 Dec 03
4
[PATCH 1/5] Remove old GNU-stack sections from nasm files.
They are not needed since the section is defined in nasm.h. --- src/libFLAC/ia32/bitreader_asm.nasm | 4 ---- src/libFLAC/ia32/cpu_asm.nasm | 4 ---- src/libFLAC/ia32/fixed_asm.nasm | 4 ---- src/libFLAC/ia32/lpc_asm.nasm | 4 ---- src/libFLAC/ia32/stream_encoder_asm.nasm | 4 ---- 5 files changed, 20 deletions(-) diff --git
2017 Jan 14
2
unsigned int and FLAC__uint32 are used interchangeably
On 1/14/17, Erik de Castro Lopo <mle+la at mega-nerd.com> wrote: > Ozkan Sezer wrote: > >> unsigned int and FLAC__uint32 are used interchangeably, leading to >> warnings with platforms (e.g. djgpp) where int32_t is long: > > Is `sizeof int == 4` though? Yes, obviously it is > I couldn't image FLAC working correctly > if it wasn't. > > Erik
2011 May 23
1
so current status of interactive PDF creation isl? trying to explore econometriic convergence thread
I think I just saw a thread go by on " how do I make interactive PDF from rgl output" but I ignored it at the time and can't seem to find consensus result on google. Essentially I wanted to create pdf or other output to share a 3D plot and let viewers interact with it but it still wasn't clear on easiest way to do this. Is this 2009 page the best reference?
2015 Jun 20
3
Future of the xapian-commits list
I spotted recently that since we switched to git, commit notifications haven't been sent to the xapian-commits list. We can probably install a hook for git to get them flowing again, but given that none of the ~20 subscribers to the list has complained, I'm wondering if a list for commits is still useful. Perhaps with a decentralised version control system it isn't, though the