09-17-2001
Do you have the source code of the DLL? Are they written in C? If yes, you may have a chance to migrate them to UNIX.
If the source code is written in C++ and they refer some class definitions other than standard C++ class (eg. MFC), it is very difficult.
If you only have the binary of the DLL in NT, of course there is no way to transfer.
Please state more specifically.
10 More Discussions You Might Find Interesting
1. Programming
Hello,
I am a VC++ programmer. I want to port my existing , working VC++ application on windows NT using MS-Word on to Unix as an OS....
My requirement is just to port the server part of the application on UNIX and client part would remain in NT.
I have many issues to handle to finally... (1 Reply)
Discussion started by: real_rachna
1 Replies
2. Programming
I have source code of a Windows C DLL. It complies properly and works. Now I need to port it to UNIX environment.
I need to know if I can create a Dynamic Library or only Static Library is possible in UNIX.
In case I can create a Dynamic Library please guide me how to proceed. Or if there... (2 Replies)
Discussion started by: ana_puri
2 Replies
3. UNIX for Advanced & Expert Users
Can anybody help me in finding out a solution for the problem below?
When we write .unix or .sh files in windows OS and port them to Unix platforms there is a character ^M inserted at the end of each line of the script file.
During ftp porting I set the transfer mode as ASCII for the script... (7 Replies)
Discussion started by: tamilselvi
7 Replies
4. Programming
We are in requirement to port relative file organization files from OpenVMS V7.1-1H2 to AIX Unix. These file contains multiple binary records each of 512 bytes but it could be possible that a few bytes are padded up to fill the record structure.
One of our thought process is to write a program... (1 Reply)
Discussion started by: S.P.Prasad
1 Replies
5. UNIX for Advanced & Expert Users
My question is: difference between unix and linux in terms of compiler, file system, ANSI
compliance, standard liabrary issues, threading issues, operating system
calls memory issues..ie whether these things wud cause problems while
porting a unix programme to linux.?
I think answer is depend... (1 Reply)
Discussion started by: prasoon
1 Replies
6. UNIX for Dummies Questions & Answers
Hi
I have a rather large set of sas programs that i want to port to unix sas.
All of these programs uses windows functionality somehow. For example win API calls and ole-dll:s via com and dcom.
Now my company is moving to sas on unix, and we must port these apps (sas macros).
So what Im... (3 Replies)
Discussion started by: iommi
3 Replies
7. UNIX for Advanced & Expert Users
Is it possible for a Unix script to execute a .dll. If so, where would I find information/examples of how to do that?
Thanks, in advance, for any help. :rolleyes: (2 Replies)
Discussion started by: BCarlson
2 Replies
8. What is on Your Mind?
I have created DLLs in c++. Is it possible to run these DLLs in unix so that I can save time converting function/scripts in unix? In this way I can reuse these DLL in Unix. Thanks. (2 Replies)
Discussion started by: alestoquia
2 Replies
9. Programming
Hello,
I am sorry to bother you all but I am thinking about switching to UNIX and I am a complete novice there.
The problem is that I need to call a C++ dll on UNIX platform which was compiled on Windows. I don't have the source code of the dll as well. I just need to call this dll in my C++... (2 Replies)
Discussion started by: clickoo
2 Replies
10. UNIX for Dummies Questions & Answers
Hi...
I have build a program for the Velleman K8000 interface card, in java, which works just fine in windows, but now I want to use the program on a Unix-System.
Is it possible to somehow convert the dll file to a format that Unix supports, or do I have to find another way?
Dll-file:... (3 Replies)
Discussion started by: Scorp-D
3 Replies
LEARN ABOUT DEBIAN
cdk_compat
cdk_compat(3) Library Functions Manual cdk_compat(3)
NAME
cdk_compat - Cdk4 compatibility functions
SYNOPSIS
SYNOPSIS
cc [ flag ... ] file ... -lcdk [ library ... ]
#include <cdk_compat.h>
int getDirectoryContents (
char *directory,
char **list,
int maxListSize);
int readFile ( char *filename,
char **info,
int maxlines);
int splitString (
char *string,
char **items,
char splitChar);
DESCRIPTION
These functions and macros make it simpler to port applications from the older Cdk4 library to Cdk5.
A few functions are deprecated in Cdk5, because they rely upon the caller to know in advance the size of data which will be returned by the
function.
Additionally, some macros are deprecated because they serve no realistic purpose: they have direct (standard) equivalents in all modern
curses implementations.
Finally, a few macro definitions are added to iron out naming inconsistencies across the Cdk4 header files.
AVAILABLE FUNCTIONS
getDirectoryContents
This opens the current directory and reads the contents. Use CDKgetDirectoryContents() in new code.
readFile
This reads a file and sticks it into the char ** provided. Use CDKreadFile() for new code.
splitString
This splits a string into one or more parts given the split character. Use CDKsplitString() for new code.
EXAMPLE
Start the porting process by changing the #include's to use
#include <cdk_compat.h>
rather than
#include <cdk.h>
Some adjustments of course are needed to make your compiler see the compatibility header file. A separate name was chosen so that it in
turn can (by adjusting the include path) include either the old Cdk4 cdk.h or the new. If the old is included, you should link your pro-
gram against the old library. Likewise, including the new requires that you link against the new library.
That is the first step: making your program compile using the compatibility header file using the old headers and library.
The next step is to get it to compile against the new headers and library. Most of the changes will require modifying bare references to
certain pointers to wrap them with the ObjOf() and ScreenOf() macros. New Cdk uses these to provide functions which are easily shared
among the different widget types. Your compiler should be able to tell you where the changes should be made. See the example programs
which are included with Cdk as a guide.
That is the hard part of porting. But even for a large program, the changes can be made simply: there are not that many types of change to
make. At the end of this step, you should still be able to build and run your program against the old headers and library. It is reason-
ably likely that you can do the same with the new headers and library. By using the same source for old/new versions of Cdk, you can test
and verify that your program still works properly after these modifications.
Finally, unless this is a purely academic exercise, you will want to remove references to the deprecated functions and macros.
SEE ALSO
cdk_objs (3), cdk_util (3)
cdk_compat(3)