similar to: dyn.load() and dyn.unload() under Windows

Hello: I'm trying to use Rcmd SHLIB to compile a single file, sann.c, to get sann.dll. I was able to get make libR.a to work, after going into MkRules and changing the line DLLTOOL=$(BINPREF)dlltool -k --as $(AS) to read DLLTOOL=C:/MINGW-1.1/bin/dlltool -k --as $(AS) But now I get: C:\rw1051\src\gnuwin32>Rcmd SHLIB sann.c make: make: Command not found make: *** [libR] Error 127

Hi every one I am working on shiny app using bnlearn for Bayesian networks and using r studio I get a fatal error and when I use R GUI I get this error ** caught segfault *** address 0xfffffffc0fcd6248, cause 'memory not mapped' Traceback: 1: .Call("mappred", node = node, fitted = fitted, data = data, n = as.integer(n), from = from, prob = prob, debug = debug) 2:

Hello: Many thanks to Professor Ripley for responding to my earlier post, included below, about trying to use mingw32 gcc.I did put back the original Rinternals.h. I am still crashing R every time I try to use C code. Here is what I did, basd on readme.packages: 1.) Ensured that C:\Rtools was first in my path, and obtained a new tools.zip from BDR's R tools site. 2.) Ensured that I

Hi Nico, Reid, and Anton, I missed the discussion when I implemented dllexport/dllimport for our local tree. I essentially implemented your approach#1. I was trying to avoid the various external_linkage + some_attribute approaches because it seems that external_linkage would imply the external linkage without the dllimport/dllexport semantics, and there may be existing compiler codes that rely on

Hello, I am using cygwin (latest version) and I managed to generate a dll partly with rcmd shlib although there was a problem with both the resouce file (I had to remove "FILEOS VOS__WINDOWS32") and the command line for gcc (--shared is not supported for instance). So I would like to know which compiler/environment you advise to use for windows OS. Then I could load the library in R

Hi everybody, me again. I'm trying to write my own VFW-like dll... It doesn't need to do much. 1.) compress a single frame and give it back to the host application 2.) host applications sends the frame 3.) client application receives frame 4.) client application tells the dll to decompress the data So if I try to do this, something is going wrong... Perhaps someone could have a look at my

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

+ruiu and compnerd, since there might be an lld issue here. A slightly simpler example. This is all x86_64; I haven't tried x86. % cat imp.c __declspec(dllimport) void ExitProcess(unsigned exitCode); int mainCRTStartup() { ExitProcess(0); } % cat kernel32.def LIBRARY kernel32 EXPORTS ExitProcess % dlltool –d kernel32.def –l kernel32.lib % cl /Zl /c imp.c % link /subsystem:console imp.obj

> > I am trying to use llvm-gcc to link shared libraries on windows/mingw32. > > When I try to link libraries that contain functions declared with > >  __declspec(dllexport) someFunction(); > > > > I get the link error: > > > >  Cannot export _someFunction: symbol not found > dllexport declspec should be put on the function definition, in this >

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 --------------

On 23.04.2013 19:10, Gao, Yunzhong wrote: > I missed the discussion when I implemented dllexport/dllimport for our local tree. I > essentially implemented your approach#1. I was trying to avoid the various > external_linkage + some_attribute approaches because it seems that external_linkage > would imply the external linkage without the dllimport/dllexport semantics, and there > may

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tried to do this, gcc complained a lot about undefined references. After a bit of mucking with the code, i came up with a few patches. This might be a good conversation starter. The build that i've got out of this does pass the testsuite. To enable LTO you just need to apply these (for non-W32 builds you probably only need one of the patches)

Hello, while improving and extending support for dllexport/import I have noticed that the current way these are implemented is problematic and I would like some input on how to proceed. Currently dllexport/dllimport is treated as linkage type. This conflicts with inlined functions because there is no linkage for the combination of both. On first though, combining both doesn't make sense, but

> I am trying to use llvm-gcc to link shared libraries on windows/mingw32. > When I try to link libraries that contain functions declared with >  __declspec(dllexport) someFunction(); > > I get the link error: > >  Cannot export _someFunction: symbol not found dllexport declspec should be put on the function definition, in this example there is nothing to export - dllexport

If building a static library, marking symbols as dllexport causes them to be exported from the final executable. For example, run objdump -x opus_demo.exe on a --disabled-shared build and look for the export table; there should not be one in a normal Win32 .exe file, but when linking static libopus, the exe exports all of the opus_* public functions. Use the libtool-defined DLL_EXPORT flag to

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:

Hi All, I have tried to write dll from window and try to implement a WineLib wrapper. BUT after compile successful, I have run the function, it show me error as below: wine: could not load L"Z:\\root\\huutri\\maintest.exe.so": Bad EXE format for Can anybody can how to solve this problem? Thank in advance The below is some code: Code: 1. windows HelloImpl.dll __declspec(dllexport)

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

I'm pretty sure I'll feel like [more of] an idiot but... Using Rgui working in a fresh, blank directory. > require(MASS) Loading required package: MASS [1] TRUE > data(cabbages) Warning message: ======> Data set `cabbages' not found in: data(cabbages) <===== > ls() [1] "last.warning" > search() [1] ".GlobalEnv" "package:MASS"