Header files for ImageIO.framework dynamic libraries.

Are individual headers available for the image io libraries (e.g. libjpeg.dylib) which are located in "/System/Library/Frameworks/ImageIO.framework/Resources". If so where can they be found?

Either get it via the Oracle client software or the instant client.
I forget what options you need to select when installing the client software -- Oracle Programmer maybe?
As for the Instant Client, download the Basic, sqlplus, and the SDK packages.
http://www.oracle.com/technology/tech/oci/instantclient/index.html
Link to download Oracle 9i software:
http://www.oracle.com/technology/software/products/oracle9i/index.html

Similar Messages

Virtualbox - install build and header files for your current kernel

I have initially installed virtualbox before upgrading the Arch
Also took backup of the kernle before upgrading since kernel26 2.6.30 is having problem with virtualbox
After upgrading I have configure the grub to use the previous kernel i.e 2.6.28
Later installed xorg and want to install the video drivers from VBox additions
but running
sh VBoxLinuxAdditions_x86.run
i get the following
install build and header files for your current kernel
The current kernel version is 2.6.28 Arch
What are the build and header files I have to install or search with pacman
And since i have upgraded the system will I able to look up the header and build files needed for kernel 2.6.28

dmartins - he's talking about his kernel's headers, not the kernel-headers package - they are two very differnet things.
sant527 - when you backed up the 2.6.28 kernel, did you remember the files in /usr/src/linux-2.6.28-ARCH/ ? They're what VBox is looking for.

Gettin header files for embedded sql

Sir,
iam acutally looking for header files needed used in embedded sql,which is used pro c* compiler .So i request you to send me a link of these files,as iam tying to learn this topic.these files are not generally available in a genaral C compiler.
So please send me reply about this and also if this particular language/techn is still being used which may help me to improve my knowledge

I am not a Cobol programmer, but I worked several years a Pro*C programmer, this precompiler issue looks very similar to others I have several times faced, when I compiled a pro*C program on different platforms, the makefile had to be tailored to fit the particular platform paths. May be this is happening to you, you should verify the compilation script and ensure the required libraries are visible.
~ Madrid

Where can i find header files for DAQ PPC Library

Hello,
First sorry for my english (I am french so ...)
I try to develope in eVB a PDA application to acquire a signal from a DAQCard-6062E (for PCMCIA), so I download card drivers (http://digital.ni.com/public.nsf/websearch/12704BA4C93584D886256F1E007135AD) but I doesn't find any header files, help files for librarie file (nirplid.dll).
Can you give me some header file (in C or in VB) or maybe a list a functions and parameters of this labrarie.

Hi,
You will find a list of all functions which can be used in LV PDA applications.
Il vous faut le module LAbVIEW PDA pour avoir accés à ces foncitons(ci-joint le lien). Sino, vous pouvez créer votre propre driver.
Salutations,
Isabelle
Ingénieur d'applications
National Instruments France

What is the meaing of the sysmbolic constant value in the header file for UIR file and how they are used

In labwindows after creating the uir then header file is create automatically. There it has define some symbolic constant. As examples of colview.h(from the examples of labwindows )
#define MAINPNL              1       /* callback function: MainPanelCB */
#define MAINPNL_RESULTS      2     /* control type: table, callback function: ResultTableCB */
#define MAINPNL_NEWTEST     3       /* control type: command, callback function: NewTestCB */
My question is how these values 1, 2 and 3 were selected and how they are used in programs ?
If anyone explains, it will be a great help.

When creating a UIR file, CVI editor takes care of assigning constants to the panels / controls you create in it.
The conceptual framework is the following (assuming to treat the file you have reported in your message):
- Within a single UIR file all panels have a unique ID, which is the one you pass to LoadPanel when loading a panel into memory. LoadPanel (0, "myfile.uir", MAINPNL); is then translated to panelHandle = LoadPanel (0, "myfile.uir", 1); , that is: "load the first panel in the uir file". The panel in memory is then assigned a handle, which is guaranted unique by the OS and saved in panelHandle variable
- Addressing a control in a panel is done e.g. using SetCtrlVal (panelHandle, MAINPNL_NEWTEST, xxx); , which again is translated to SetCtrlVal (panelHandle, 1, 3); that is: "Set control #3 in the panel identified by panelHandle to value xxx".
You must not modify the include file associated to the UIR as it is fully maintained by the IDE and is rewritten each time you save the UIR file.
That conceptual framework has some advantages and some caveats:
- You can load the same panel more then once in your program: each instance is independent from the others as each panel handle is unique; in some occasions it may be helpful, e.g. if you need to handle several identical equipments connected to your PC and you can load the same control panel for each unit connected maintaining each of them independent
- If the panel handle is wrong, the system does not warn you of this as it does not know of the symbolic names you are using; if you try that SetCtrlVal command with a wrong handle you are trying to manipulate a control on a panel different from the one you intend: supposing actual panel idientified by the handle has control #3 the maximum you can expect is that you receive an error in case you pass e.g. a string to a numeric, but if controls are of the same type you have no errors or warning at all! This is particularly important when addressing controls on pages of a tab control: each page is really a separate panel with its proper handle that you must retrieve with GetPanelhandleFromTabPage command before addressing the controls on it
Proud to use LW/CVI from 3.1 on.
My contributions to the Developer Zone Community
If I have helped you, why not giving me a kudos?

Ther are PARAMETER LIST DISCREPANCIES in the help file vs the NIDAQ.H header file for GPCTR_Read_Buffer...

PROBLEM: The function help file contains documentation for using GPCTR_Read_Buffer with 7 parmeters in the parameter list. The NADAQ.H Header file contains 8 parameters in the function declaration. Which is right? What is the correct parameter list and can an example be provided that shows how to use the function correctly? I am currently using DAQ ver 6.92 and a 6602 Counter Timer board in a buffered start/stop or ND_BUFFERED_TWO_SIGNAL_EDGE_SEPARATION_MSR application.

Thanks for the response Filipe, I'll let you know how it goes. I only went into the header file because example code provided by NI ... paste ...
iStatus = GPCTR_Read_Buffer(iDevice, ulGpctrNum, ND_READ_MARK, ulReadOffset, ulNumPtsToRead, ulTimeOut, &ulNumPtsRead, pulReadBuf);
showed use of 8 parameters - in agreement with the header file and in disagreement with the on-line help file function documentation.
Tom

[SOLVED] Location of header files (for vmware tools)

Attempting to install VMWare Tools (http://www.vmware.com/support/ws5/doc/w … linux.html) for my Archlinux guest, encountered this question:
What is the location of the directory of C header files that match your running
kernel? [/usr/src/linux/include]
I found a few old posts saying to use the AUR package, but I can't per my divisions linux server policies (no non-official repositories). Are these included by default, or do I need to get them via some package? Is this kernels-26-headers package, or similar?
Last edited by Intrepidus (2010-10-25 22:38:07)

Thanks, that got me a bit farther than before. I've now gone from that error to this error:
The directory of kernel headers (version @@VMWARE@@ UTS_RELEASE) does not match your running kernel (version 2.6.35-ARCH). Even if the module were to compile successfully, it would not load into the running kernel.
This was after pointing it to /usr/src/linux-2.6.35-ARCH/include. Any ideas what the story is now?
EDIT: Had to copy utsrelease.h and autoconf.h to version.h and autoconf.h, respectively, to /usr/src/linux-2.6.35-ARCH/include/linux.
Last edited by Intrepidus (2010-10-25 22:17:10)

Header file for GUI in CVI

Hi
        I have created the GUI by adding different controls. When I make some changes in that
xxx.uir file and save it, it automatically do the changes in xxx.h file.
But If want to #define the values for all the controls, how to do that.
For eg :
Autogenerated xxx.h file has
#define PANEL                                          1
#define PANEL_CHECKBOX_1                   2
#define PANEL_CHECKBOX_5                 3
#define PANEL_LED_1                              4
#define PANEL_CHECKBOX_2                  5
#define PANEL_CHECKBOX_3                 6
#define PANEL_LED_2                             7
#define PANEL_CHECKBOX_4                8
But I want to edit it like
#define PANEL                                          1
#define PANEL_CHECKBOX_1                   2
#define PANEL_CHECKBOX_2                   3
#define PANEL_CHECKBOX_3                   4
#define PANEL_CHECKBOX_4                   5
#define PANEL_CHECKBOX_5                   6
#define PANEL_LED_2                               11
#define PANEL_LED_1                              12
Is it possible to do that?
Please any one help me on this
Regards
NB
Solved!
Go to Solution.

Hi Nagraj,
The autogenerated gui header files should not be edited directly.
CVI assigns control IDs according to their tab order in the UIR panel.
To modify the tab order, activate the panel you want to edit and press Ctrl + T.
This opens a tab-order-editor where you can set the tab order simply by clicking the controls in that desired order.
After you save the file, the header gets refreshed with the new control IDs.
Hope this helps,
P.S: If you want to change these control IDs just to access them in a loop,
I suggest you to put the control IDs in an array and then use the for loop variable as the array's index.
e.g:
int i;
int ctrlArr[5] = {PANEL_RUN_BUTTON, PANEL_LED, PANEL_RING, PANEL_TABLE, PANEL_STOP_BUTTON};
for (i=0; i<5; i++)
// good
SetCtrlAttribute (panel, ctrlArr[i], ATTR_DIMMED, 0);
// bad
// SetCtrlAttribute (panel, i, ATTR_DIMMED, 0);
S. Eren BALCI
www.aselsan.com.tr

Where to find opengl header files for nvidia driver

My laptop (Dell Inspiron 6400) has an nvidia card and uses the nvidia driver (Ver 177.82). Where can I find the opengl header files appropriate to the nvidia driver? The gl.h i have in /usr/include/GL is the Mesa version.

Thanks. Guess i will have to download the driver package from Nvidia and extract the headers from that.

Shared library: function is not found and recognized in header file

Hello,
I am trying to use Java methods into LV. I am doing so by creating Java Invocation Interface, usind which I can call Java methods into C++ and then create a shared library that can be called into LV.
When I am importing my shared library into Labview, I am getting the following error messages:
The shared library contains 3 function(s). But no function is found and recognized in the header file. The following function(s) cannot be wrapped. If you want to import these functions, please review the warning messages next to the functions below. You will need to fix the problems before you can continue with the wizard.
jclass invokeJavaClass(JNIEnv* jenv, string className);
The following symbols are not defined:
jclass;
Undefined symbols can prevent the wizard from recognizing functions and parameters. To correct this problem, check the header file to determine if you must add preprocessor definitions. Click the Back button to return to the previous page of the wizard to add a preprocessor definitionsl (for example, "NIAPI_stdcall = __stdcall" or "NIAPIDefined = 1").
The following header file was not found in the specified header file or one of the referenced header files:
- string
- iostream
- cstring
- jni.h
To fix, click the Back button to go to the previous page and add the header file path to the Include Paths list.
Please advise.
Regards,
H
Attachments:
SharedLibError.png ‏51 KB

Hello Vivek,
The LabVIEW dll that I am trying to import does not include any third-party device..all my code is fully based on LabVIEW. Maybe this helps you to guess what is happening: once I've parsed the dll' header appears an error
like this one:
void
__cdecl Zdmt(LVBoolean *stop, double P, char channelName[],
    TD1
*errorIn, TD14 *FFTOptions, TD12 *Calibration, char FileName[],
int32_t minRecordLength, TD26 *InstrumentHandler, LVRefNum
sessionRefArray[],
    LVRefNum *queueIN, TD1 *errorOut, LVBoolean
*averagingDone,
    HWAVES LastRecordFetched, TD24 *Impedance, TD17
*ColeColeCluster,
    TD18 *FFTcluster, TD5
*InstrumentHandleOutputCluster, LVRefNum *queueOut,
    int32_t
*Acquired, TD6 *FreqTimeInfoCluster, double *averagesCompleted,
int32_t len);
The following symbols are not defined:
LVBoolean;
int32_t; LVRefNum;
Undefined symbols can prevent the wizard
from recognizing functions and parameters. To correct this problem,
check the header file to determine if you must add predefined symbols.
Click the Back button to return to the previous page of the wizard to
add a preprocessor definitionsl (for example, "NIAPI_stdcall =
__stdcall" or "NIAPIDefined = 1").
The following header file was
not found in the specified header file or one of the referenced header
files:
- extcode.h
To fix, click the Back button to go to the
previous page and add the header file path to the Include Paths list.
I have replaced the first line #include "extcode.h" of
the dll header file for #include "C:\Program Files\National
Instruments\LabVIEW 8.6\cintools\extcode.h" that is the full path where
the header file is located. However, new libraries seems to be missed:
- stdint.h
- MacTypes.h
As far as I know, Mactypes.h contains basic mac os data types and it doesn't have any relation with stdint.h...
I have created both of them and stored into the same folder as extcode.h, but then other libraries are missed!!!
Do you know if it would be possible to create the .dll generating all the header files associated for its data structures???
And if this is not factible, then what do you suggest me? because I hope to not having to create all the header files until it stops giving me an error!
thanks for four time,
ben

Including Header files

Hi
Am a mainframe guy and new to these stuffs.
Now ,I want to compile a C++ program in Sunstudio.
My question is how & where to add the header files ?
What is the extension to be used for the header files ?
Please someone help me in this regard.

[I had replied to this yesterday but it didn't appear to show up in the thread]
The header file is added to the 'Header files' in the same project For Sun Studio, I am pretty sure that the header files listed in the project
is not used by the compiler to find the header files.
That list of header files is merely a convience for the programmer
as a reference and to quickly find and open header files used in the project.
You need to tell the IDE which directories to search for header files
(that are not standard header files)
I am presuming that the header file(s) the compiler is complaining about is not a standard library header file,
but instead is a header file associated with the source code you are compiling or are associated with
a 3rd party library required by the program.
The #include semantics, as ralphw mentioned, can be a little complex.
As a quick follow up to ralphw's response
generally #includes of the form
#include "foo.h"
indicates that the header file is in the same directory as your project source files.
Normally the compiler can find this file with some simple seach heuristics so
I suspect the offending include line is of the form:
#include <foo.h>
The <> brackets indicates that the header file is in a directory to be specified
in one of the listed include directories.
Include directories may be intrinsic to the compiler implementation
such as standard libraries and/or libraries added by the compiler vendor;
or they may be header files for 3rd party libraries or your own libraries
stored in some directory other than the application program you are compiling.
For 3rd party libraries or your own libraries, provide a list of
directories to seach for included header files.
for command line mode, in almost all c/c++ compilers these directories are listed with
the -I command line argument.
In SunStudio 12, you list the include directories in
your project properties / Parse configuration / Sun C++ compiler / General / Preprocessor definitions
If you have further questions on this, it would be helpful to know
if you are attempting to compile some preexisting code
or are you creating code from scratch.
(It sounds like you are compiling preexisting code that
presumably has been compiled correctly in some other implementation
and are trying to port it to Sun Studio.
If this is the case, it sounds like you simply need to add the
path of the directory containing the offending header file to
this list of include directories.)
It would also be helpful to know the fully qualified
file name of the offending .h file,
and the form of the #include line in the file that is being compiled.
If the #include line is of the form
#include <dir/foo.h> then you need to add the
path of the 'dir' parent directory to the include directories list.

Missing header files when importing a shared library with labview 8.6?

Hi all,
I want to import a .dll into my .vi program but I am not able to do it...
I have created the dll following the ni website tutorial
http://zone.ni.com/devzone/cda/tut/p/id/3303#toc2
Once the dll has been created, I have tried to import it with
Tools-Import-Shared Library(dll)
After parsing the header file appears an error like this one:
void __cdecl Zdmt(LVBoolean *stop, double P, char channelName[],
    TD1 *errorIn, TD14 *FFTOptions, TD12 *Calibration, char FileName[],
    int32_t minRecordLength, TD26 *InstrumentHandler, LVRefNum sessionRefArray[],
    LVRefNum *queueIN, TD1 *errorOut, LVBoolean *averagingDone,
    HWAVES LastRecordFetched, TD24 *Impedance, TD17 *ColeColeCluster,
    TD18 *FFTcluster, TD5 *InstrumentHandleOutputCluster, LVRefNum *queueOut,
    int32_t *Acquired, TD6 *FreqTimeInfoCluster, double *averagesCompleted,
    int32_t len);
The following symbols are not defined:
LVBoolean; int32_t; LVRefNum;
Undefined symbols can prevent the wizard from recognizing functions and parameters. To correct this problem, check the header file to determine if you must add predefined symbols. Click the Back button to return to the previous page of the wizard to add a preprocessor definitionsl (for example, "NIAPI_stdcall = __stdcall" or "NIAPIDefined = 1").
The following header file was not found in the specified header file or one of the referenced header files:
- extcode.h
To fix, click the Back button to go to the previous page and add the header file path to the Include Paths list.
I have replaced the first line #include "extcode.h" of the dll header file for #include "C:\Program Files\National Instruments\LabVIEW 8.6\cintools\extcode.h" that is the full path where the header file is located. However, new libraries seems to be missed:
- stdint.h
- MacTypes.h
Does anybody know what I have to do??
Any help will be really appreciated,
Regards,
Benjamin

If you use any of the LabVIEW cintools headers, they reference other headers too. The import wizard is written in a way that it simply skips parsing datatypes that can not be resolved due to missing header files. If your functions you want to import references such datatypes then you get an according error about any include files the wizard could not load, otherwise not. The wizard can not know which of the missing header files is the problem since it obviously doesn't know what would be in those header files.
The LabVIEW cintools headers are multiplatform, meaning they evaluate various compiler predefined defines to determine which platform they are included in. The import library wizard does not define any specific defines, since it is not really a compiler. So you have to define them. And they get adapted with each new LabVIEW version to support new compilers and compiler versions, so the defines described in the link in the first post do not have to be correct for cintools headers in newer LabVIEW versions.
All in all writing DLLs that interface to LabVIEW cintools headers should not be done by writing them and then importing them using the wizard but instead you should write the VI and create the Call Library Node, then let LabVIEW create a template C file from the context menu of the Call Library Node and copy that into your C sources and fill in the functions from there.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Xmlstarlet and header files confusion

I'm trying to make a package out of xmlstarlet. Just running configure and then make has me running into this error:
ad /usr/lib/libxml2.a -lz -lm -lpthread -ldl -L/usr/lib
/usr/lib/libexslt.a(crypto.o): In function `exsltCryptoGcryptInit':
crypto.c:(.text+0x15c): undefined reference to `gcry_check_version'
/usr/lib/libexslt.a(crypto.o): In function `exsltCryptoRc4DecryptFunction':
crypto.c:(.text+0x2d4): undefined reference to `gcry_cipher_open'
crypto.c:(.text+0x2fe): undefined reference to `gcry_cipher_ctl'
crypto.c:(.text+0x327): undefined reference to `gcry_cipher_decrypt'
crypto.c:(.text+0x333): undefined reference to `gcry_strerror'
crypto.c:(.text+0x36f): undefined reference to `gcry_cipher_close'
crypto.c:(.text+0x47c): undefined reference to `gcry_strerror'
crypto.c:(.text+0x4bc): undefined reference to `gcry_strerror'
/usr/lib/libexslt.a(crypto.o): In function `exsltCryptoRc4EncryptFunction':
crypto.c:(.text+0x60f): undefined reference to `gcry_cipher_open'
crypto.c:(.text+0x639): undefined reference to `gcry_cipher_ctl'
crypto.c:(.text+0x668): undefined reference to `gcry_cipher_encrypt'
crypto.c:(.text+0x674): undefined reference to `gcry_strerror'
crypto.c:(.text+0x6b0): undefined reference to `gcry_cipher_close'
crypto.c:(.text+0x814): undefined reference to `gcry_strerror'
crypto.c:(.text+0x854): undefined reference to `gcry_strerror'
/usr/lib/libexslt.a(crypto.o): In function `exsltCryptoSha1Function':
crypto.c:(.text+0x90c): undefined reference to `gcry_md_hash_buffer'
/usr/lib/libexslt.a(crypto.o): In function `exsltCryptoMd5Function':
crypto.c:(.text+0xa0c): undefined reference to `gcry_md_hash_buffer'
/usr/lib/libexslt.a(crypto.o): In function `exsltCryptoMd4Function':
crypto.c:(.text+0xb0c): undefined reference to `gcry_md_hash_buffer'
collect2: ld returned 1 exit status
make[2]: *** [xml] Error 1
make[2]: Leaving directory `/tmp/xmlstarlet-1.0.1/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/xmlstarlet-1.0.1'
make: *** [all-recursive-am] Error 2
Now, I don't know how to interpret that error, but the Soureforge page does contain the following advice which I figured might be pertinent:
Make sure that libxml2 and libxslt header files matches (by version) with libraries you are linking. The versions of include files can be found in ${include_prefix}/libxml2/libxml/xmlversion.h and ${include_prefix}/libxslt/xsltconfig.h
Using find I came up with the files
/usr/include/libxslt/xsltconfig.h
/usr/include/libxml2/libxml/xmlversion.h
and digging into them made it clear that libxml was version 2.6.32 and libxslt was 1.1.24. But I don't knwo how to match that? Or if this is even remotely relevant to the error message, I'm seeing?

chochem wrote:bugger... I just submitted it but I can't find any way to submit my .install file alongside it - any hints?
Just include it in your package and resubmit it (the new package will replace the old one). Also, MIT is not a standard license so you need to store a copy of it in /usr/share/licenses/<package name>/ (read the wiki for more information on this).

What's the largest header file in /usr/include/sys?

Just noticed this,
$ ls -l /usr/include/sys | sort +4n | tail -3
-rw-r--r--   1 root     bin        59151 Jul 4 03:39 dtrace_impl.h
-rw-r--r--   1 root     bin        76941 Jul 4 03:39 sunddi.h
-rw-r--r--   1 root     bin        83768 Jul 4 03:39 dtrace.hwhich is great because dtrace.h is so rich with comments, and dtrace_impl.h has plenty of ASCII art. Hooray!
This more than makes up for the sins of /usr/include/sys/tnf_probe.h! ;-)
.... now if you guys are ever bored, feel free to update /usr/include/sys/swap.h, /usr/include/vm/anon.h ... :-)
Brendan

Sorry I was really busy the last few days. Thank you for your answers!
I probably should have left out all the specifics of what the software was that I was packaging, because I think what I was really asking did not come across clearly. What I really wanted to know is:
Why do I have to provide the "-I /usr/include/headers_dir" compiler option for some libraries but not for others, although the header files for each lie in a level 1 subdir of /usr/include?
I thought that maybe there was some kind of index of installed libraries that I didn't know about, which I could have updated from within PKGBUILD (so I guess that's why I included it originally). Seems to me now, though, that this is not the case.
I did put in some google time (but not lots b/c 1. hard to google and 2. busy) to find an answer, but to no avail and it's not really top priority right now (and quite honestly never will be, since there is the -I option), so I guess it'll have to wait, unless someone knows...
---EDIT---
So, right after I posted this (stupid me) I had a little think and I finally understand, whats happening.
1. Headers are not found without specifying the directory they are in.
2. I need the -I option because easykf headers are not well formed.
Thanks a lot!
Last edited by maximax (2013-09-27 00:26:03)

What is the .plist file for view options?

Can't pick a background color after Lion instsll. Thought this might correrct it? Yes?

hi uttam
the sar file for defalut framework is
SCSCLIENTEP_5-20000497.SAR & MMC_0-20000497.SAR
this file u will get from service.sap --> software download
search for SAP STARTUP FRAMEWORK 6.20
and the related note for it is
not number 687485
regards
Janak Mehta

Header files for ImageIO.framework dynamic libraries.

Similar Messages

Maybe you are looking for