cross-plat version of _wfullpath() - libc

is there a cross platform version of _fullpath() which is windows specific function? looking for a portable library function for this.
tried realpath() but this is supported for linux and Mac but not for windows.

Related

Does the MSYS2 version of emacs support X server?

MSYS2 has three versions of emacs. Only the msys/emacs version supports term mode and other shell related features. The mingw32 and mingw64 versions only support the inconvenient shell and eshell mode.
However, the msys version does not seem to support GUI. In Cygwin it was possible to access GUI by installing an X server. Does the MSYS2 version supports X server? How to configure this version?
If you're willing to use cygwin, it now offers a cygwin version of emacs that supports a native Windows gui (emacs-w32); no need for an X-server!

Run DITA OT in Mac OS?

The DITA OT documentation has quite a bit of information about how to run the DITA OT in a Windows environment, but not much at all about running it in Mac OS. What is the procedure for running it in Mac OS (Mountain Lion)? Especially if you need to set environment variables (which is kind of tricky in Mac OS)
DITA-OT installation for OS X is documented in DITA-OT user guide.

solaris library in windows

We have got a solaris shared object(.so) compiled using sun studio creator[Sun C++ 5.10] (no access to source code).
I have to develop c++ application based on that solaris library in windows using ide's eclipse cdt/visual studio.
Preferably eclipse cdt.
Tried using Mingw not woring.
Can g++ from MinGW link to sun studio library.
I hope you aren't expecting something as simple as a linker flag ...
You have here incompatible formats (ELF vs PE), incompatible ABIs (Solaris vs Windows) and possibly incompatible machine code (SPARC vs x86 vs x64).
If the library is suitable for that, the "simplest" solution would be to create a helper service running on a Solaris server that expose the library function as RPCs, and consume them on Windows.

installing Win32::OLE on mac os x

Mac OS X supports Microsoft OLE.
Does anyone know if it's possible to install the Win32::OLE perl module on mac OS X?
I know the module isn't supported on Mac, but would it be possible to try and compile anyway?
I don't think so that Mac Os X supports Microsoft OLE nativly. I think, it is some kind emulating or something like that.
Win32* modules checks the osversion ($^O if I am correct) to detect which os is run.
With force and without tests you could install this module but I think is won't work after install.
If you have an evidence that Mac OS X supports MS OLE please link that article into your question and you could ask the module maintainer to support OSX if it is really support OLE.
regards,
Modules in the Win32:: namespace, are for modules that work directly with Windows.
This means that it won't work on anything that doesn't present itself as Windows.
You could use a Win32 build of Perl running under WINE. Note that this would only be able to work with Windows versions of a program that are also running under WINE. (Assuming you can get it to work at all.)

Compiled perl executable fails to run on Windows 7 (64 bit)

I have created an executable (.exe) of a perl script on a 64-bit linux kernel. It executes correctly in this environment.
When the executable is run in 64-bit Windows 7, the following error message is displayed:
The version of this file is not compatible with the version of Windows
you're running. Check your computer's system information to see
whether you need x86 (32-bit) or x64 (64-bit) version of the program,
and then contact the software publisher.
Given that the source and destination OS's were both 64-bit, I'm not sure that the architecture of the build is the issue. Are there any special considerations to make a compiled perl program execute properly in Windows? Thank you.
Executable files are not compatible across platforms. They will run on the original platform only unless they are explicitly cross-compiled to a different target. That's actually the reason we use interpreted languages. What you want to do is not possible because the Windows and Linux APIs, libraries, and well just about everything are completely different.
This is why you need to download a different version of a program for linux/windows/mac.