Sponsored Content
Operating Systems Linux Linux Shared Library build question... Post 302568451 by Corona688 on Thursday 27th of October 2011 10:36:20 AM
Old 10-27-2011
Sorry, missed your question.

Code is generated during the compilation phase, so if you want this code to be position independent, you have to tell the compilation phase...
 

10 More Discussions You Might Find Interesting

1. Programming

Shared Library

hello all I want to work in shared libraries how can i work in Linux Environment ? (2 Replies)
Discussion started by: rajashekaran
2 Replies

2. SCO

Creation of Shared library

Hi all, I am new to sco unix. I would like to know abt the procedure to create shared library in Sco-unix. Is it differ from linux? any help?? Thanx in Advance!!!!! (0 Replies)
Discussion started by: sarangb
0 Replies

3. UNIX for Advanced & Expert Users

shared library

What is the primary difference between static library and dynamic library? and how to write static shared library? (1 Reply)
Discussion started by: areef4u
1 Replies

4. Programming

Shared memory in shared library

I need to create a shared library to access an in memory DB. The DB is not huge, but big enough to make it cumbersome to carry around in every single process using the shared library. Luckily, it is pretty static information, so I don't need to worry much about synchronizing the data between... (12 Replies)
Discussion started by: DreamWarrior
12 Replies

5. Programming

Using funcion in a shared library

Is there any way in C to access a function in C shared library. I have used dlopen to access /load the c shared library but unable to use the function in the shared object. Thanks in advance :b: (1 Reply)
Discussion started by: yhacks
1 Replies

6. Programming

Shared memory for shared library

I am writing a shared library in Linux (but compatible with other UNIXes) and I want to allow multiple instances to share a piece of memory -- 1 byte is enough. What's the "best" way to do this? I want to optimize for speed and portability. Obviously, I'll have to worry about mutual exclusion. (0 Replies)
Discussion started by: otheus
0 Replies

7. HP-UX

Shared Library Issue HP UX

I have never seen this issue before, but here is what is happening. I link an executable against two dynamic mlib libraries veclib and lapack. We place a newer version of these libraries in a write only directory and point the shlib_path at that directory. When the executable runs, it gets a... (3 Replies)
Discussion started by: sambarusty
3 Replies

8. Shell Programming and Scripting

How to change a Makefile from building static library to shared library?

Hi: I have a library that it only offers Makefile for building static library. It built libxxx.a file. How do I in any way build a shared library? (either changin the Makefile or direct script or command to build shared library) Thanks. (1 Reply)
Discussion started by: cpthk
1 Replies

9. Programming

Shared library with acces to shared memory.

Hello. I am new to this forum and I would like to ask for advice about low level POSIX programming. I have to implement a POSIX compliant C shared library. A file will have some variables and the shared library will have some functions which need those variables. There is one special... (5 Replies)
Discussion started by: iamjag
5 Replies

10. AIX

Add shared members from library to same library in a different directory

I'm trying to install libiconv to AIX 7.1 from an rpm off of the perzl site. The rpm appears to install but I get this error message. add shr4.o shared members from /usr/lib/libiconv.a to /opt/freeware/lib/libiconv.a add shr.o shared members from /usr/lib/libiconv.a to ... (5 Replies)
Discussion started by: kneemoe
5 Replies
mlib_SignalUpSample_S16_S16(3MLIB)			    mediaLib Library Functions				mlib_SignalUpSample_S16_S16(3MLIB)

NAME
mlib_SignalUpSample_S16_S16, mlib_SignalUpSample_S16S_S16S, mlib_SignalUpSample_F32_F32, mlib_SignalUpSample_F32S_F32S - signal upsampling SYNOPSIS
cc [ flag... ] file... -lmlib [ library... ] #include <mlib.h> mlib_status mlib_SignalUpSample_S16_S16(mlib_s16 *dst, const mlib_s16 *src, mlib_s32 factor, mlib_s32 phase, mlib_s32 n); mlib_status mlib_SignalUpSample_S16S_S16S(mlib_s16 *dst, const mlib_s16 *src, mlib_s32 factor, mlib_s32 phase, mlib_s32 n); mlib_status mlib_SignalUpSample_F32_F32(mlib_f32 *dst, const mlib_f32 *src, mlib_s32 factor, mlib_s32 phase, mlib_s32 n); mlib_status mlib_SignalUpSample_F32S_F32S(mlib_f32 *dst, const mlib_f32 *src, mlib_s32 factor, mlib_s32 phase, mlib_s32 n); DESCRIPTION
Each of these functions performs upsampling. For monaural signals, the following equation is used: dst[i] = src[k] if i == k*factor + phase dst[i] = 0 if i != k*factor + phase where k = 0, 1, ..., (n - 1); i = 0, 1, ..., (n*factor - 1). For stereo signals, the following equation is used: dst[2*i] = src[2*k] if i == k*factor + phase dst[2*i] = 0 if i != k*factor + phase dst[2*i + 1] = src[2*k + 1] if i == k*factor + phase dst[2*i + 1] = 0 if i != k*factor + phase where k = 0, 1, ..., (n - 1); i = 0, 1, ..., (n*factor - 1). PARAMETERS
Each of the functions takes the following arguments: dst Output signal array. src Input signal array. factor Factor by which to upsample. factor >= 1. phase Parameter that determines relative position of an input value, within the output signal. 0 <= phase < factor. n Number of samples in the input signal array. RETURN VALUES
Each of the functions returns MLIB_SUCCESS if successful. Otherwise it returns MLIB_FAILURE. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Committed | +-----------------------------+-----------------------------+ |MT-Level |MT-Safe | +-----------------------------+-----------------------------+ SEE ALSO
mlib_SignalDownSample_S16_S16(3MLIB), attributes(5) SunOS 5.11 2 Mar 2007 mlib_SignalUpSample_S16_S16(3MLIB)
All times are GMT -4. The time now is 01:42 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy