02-21-2005
HP-UX to linux porting
Hi all,
i wanted to port some HP-UX code to linux. can anybody point to some documents or resources that would help me in doing the porting..
thanks in advance
Arun Prakash
10 More Discussions You Might Find Interesting
1. Programming
I need port Win32 console application, which was developed with MS Visual Studio 6.0 (without MFC using) into Linux. What is the best way to port project? Are there any standard tools or decisions?
Thank you in advance,
Sergey (0 Replies)
Discussion started by: Sergeyy
0 Replies
2. Programming
Gents,
i'm a senior applications developer and need to port a Linux server application ( no additional / special libraries or unique header files ) to a HPUX enviroment.
Any chance to compile it on the Linux using flags to create an HPUX binary with gcc? (8 Replies)
Discussion started by: anak0nda
8 Replies
3. Linux
helo,
i m porting HP-UX socket application to Linux SSL-socket application.
I have use htonl() in HP-UX.
so when i use it in Linux, data transf is not done and application become soem time crashed.
now when i remove htonl() in linux, then i got data but it will not proper order or some data may... (1 Reply)
Discussion started by: amitpansuria
1 Replies
4. Linux
Hello All,
I have a code of DHCP which is implemented on Linux. During porting this code from Linux to VxWorks, I come up with following errors:-
jects\freedom\ap\udhcp\socket.c
C:\projects\freedom\ap\udhcp\socket.c: In function `read_interface':
C:\projects\freedom\ap\udhcp\socket.c:79:... (1 Reply)
Discussion started by: Sunny Shivam
1 Replies
5. Programming
I am new to Linux programming and my work involves changing an abstraction layer which made Nucleus calls, to Linux calls.
In Case of Events Nucleus has calls like
NU_Set_Events()
NU_Retrieve_Events()
Can I use the POSIX thread conditional variables for Linux?
Can I use the System V calls... (1 Reply)
Discussion started by: taklubaba
1 Replies
6. Filesystems, Disks and Memory
Hi,
I was trying to port efs_mount(OSE system call) to a LInux.The efs_mount function is used to mount a volume on the indicated device dev.Upon successful completion of this OSE sytem call a volume manager (VM) will be available through which files on this volume are accessed. The Syntax for... (4 Replies)
Discussion started by: roshantraj30
4 Replies
7. Solaris
Hi all,
Has anyone experience with proting a Linux driver (C-code) to Solaris 10?
I have a Sunix SATA card with a inicio1622 chipset, but no driver available. From the website of inicio I downloaded the drivercode for Linux 2.4.
Having done some investigation I found a Solaris driver... (4 Replies)
Discussion started by: longwave
4 Replies
8. Shell Programming and Scripting
Can any one please help the use of "cu command in Solaris" and as well as in Linux :confused: (1 Reply)
Discussion started by: sabee.prakash
1 Replies
9. Programming
I am challenged with porting an old application from Solaris to Red Hat. The application uses Rogue Wave and I am searching for a Red Hat implementation. Your help is appreciated! (2 Replies)
Discussion started by: FunkyWinkerbean
2 Replies
10. Shell Programming and Scripting
I have a script which has commands that are located in different paths on my Linux o/s than on Solaris. For example, to make uname work, I need to do it this way in Solaris:
my $host= `/usr/bin/uname -n` But in Linux it is:
my $host = `/bin/uname -n`I have this issue with at least 5... (8 Replies)
Discussion started by: newbie2010
8 Replies
LEARN ABOUT DEBIAN
getdirectorycontents
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)