Dim in Shared Library is not CustomXTopMember or EnableCustomXAggregation properties

Similar Questions

• How to include the shared library of BlackBerry in a native extension WebWorks

  I developed a native extension WebWorks that works very well on Simulator and devices when included in a webworks app.

  I also have a sample of waterfalls project with the same code base that I use to test the WebWorks extension code.

  Since a large part of the code is reusable, I decided to create a shared library of BlackBerry, so I can reuse in other projects. When I include the NEW shared library in the waterfalls and then everything works well, as before.

  When I include it in the extension WebWorks it draws very well. The .so file size was much smaller and that worried me (I suspected that the shared library was not included in there). But since its construction very well I went trying to run my application webworks. When it came to hitting the extension I got a ' need of error. Cannot find the library of blah/blah/...so'.

  I had this before and found out that it was because the dependent QT libraries have not been correctly referenced. It so that the shared library is not properly referenced/copied /-thing... This event is supported? For example, by using a custom in a WebWorks extension shared library?

  It worked

  Version 2 is almost right

  In the library paths pane Add...

  ${workspace_loc: / / extlibs/device$ {ProjName}}

  for peripheral and do Simulator

  ${workspace_loc: / / extlibs/Simulator of ${ProjName}}

  Always with libname in libraries

  I just linked to unrar successfully like this library

  Whew - they do this hard work of stuff

• Error during import Shared Library: library specified for this node was not found or could not be loaded

  Hello

  I use LV-2009 for Linux. I am creating a Wrapper Vi. I have a simple addition of C++ function that I created a .h header file and a shared .so library. After you import the shared library, I get an error report, I joined here (Report.doc).

  When I right click on the Subvi and click on configure to mention the .so library path, I see a window saying "file not found. The file may have been moved or delete", even though I have this library in the path that I've specified.

  I've attached a screenshot of the error I get. Please suggest what can be done.

  Thank you.

  Kind regards

  -H.

  
  

  
  

• QDE Launcher executable not found his companion shared library

  Hello world

  I recently instaled Cascades SDK on Ubuntu 12.10 when I tried to open bbndk.sh or bbndk_admin.sh im this error

  executable Launcher Qde did not find its shared library of companion

  I tried to unstall it and reinstall but the same error: s

  Thanks in advance

  I solve it I re download the SDK, I think that one has been tampered

• When deploying Shared Library, my Trinity - config.xml is not included

  Hello
  
  I've implemented my own Skinning in a little project I will deploy as a shared library.
  
  I defined my xml/css files
  

  custom.css
  trinidad-config.xml
  trinidad-skins.xml

  I created my deployment profile and set it as the library of the ADF.
  
  My only problem when I look at the generated jar, my Trinity - config.xml was not included?
  
  Any reason?
  
  Context passing:
  I intend to deploy it as a shared library in WLS so that I could drop it in my Webcenter portal.
  I posted the question to the JDeveloper forum because I thought it's more Jdev problem and not that of the webcenter.
  
  Any thoughts?
  
  Thank you

  Neliel,

  According to the literature [url http://docs.oracle.com/cd/E16162_01/user.1112/e17456/adfsg_apply.htm#BGBCDGGA], trinidad - config.xml doesn't get packed in a JAR library for skin.

  John

• Simple shared library (not webapp without changes MANIFESTS) does not work.

  just starting to move from OC4J to BEA. We are on Weblogic 10.3.
  
  I have a simple JAR (supplied by seller) that I intend to use as a shared library (ibmjndi.jar). I do not play with the MANIFESTO.
  
  
  
  
  [http://download.oracle.com/docs/cd/E11035_01/wls100/programming/libraries.html#wp1065473 | http://download.oracle.com/docs/cd/E11035_01/wls100/programming/libraries.html#wp1065473] indicates that I can deploy "a simple Java class or classes bundled in a JAR file.
  
  Deployment library appears in my summary of deployments, status = Active, type = library. his name is ibmjndi.
  
  I've implemented an itty-bitty webapp to use ibmjndi. I have this weblogic.xml:
  

  <?xml version = '1.0' encoding = 'windows-1252'?>
  <!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN" "http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd">
  <weblogic-web-app>
   <reference-descriptor>
    <library-ref>
     <library-name>sjtc</library-name>
    </library-ref>
    <library-ref>
     <library-name>ibmjndi</library-name>
     <exact-match>false</exact-match>
    </library-ref>
   </reference-descriptor>
  </weblogic-web-app>

  When I try to deploy this WAR, I get this:
  

  An error occurred during activation of changes, please see the log for details.
  Message icon - Error Failed to load webapp: 'eleveng.war'
  Message icon - Error Error: Unresolved Webapp Library references for "ServletContext@9169688[app:eleveng module:eleveng.war path:/eleveng spec-version:2.5]", defined in weblogic.xml [Extension-Name: ibmjndi, exact-match: false]

  the is
  
  what Miss me?
  
  Published by: user8652010 on February 10, 2011 08:43

  You use the correct library name in the file application.xml - weblogic as
  "hibernate3.

  Note: the name of the library we define for our library while deploying by using "weblogic. Program deployment"utility or as shown above using the Ant:

  Or define library name in "META-INF\MANIFEST. MF' of your Jar file.

  .
  .
  Thank you
  Jay SenSharma

• shared library issues

  Hello

  I have a DLL to my amp and a help file and a header file, but when I try to import the shared library, it has all the functions... Now, I have some functions to a third party, but when I try to:

  getinstancelist-> opendevice-> getsignalformat->-> device nearby stopdevice

  Often, my entire LabVIEW program stops and gives an error. I wish I could do all the functions with the wizard, so that I can be shure that all is well done...

  In the room attached of the SDK, DLL and header files + getinstancelist, opendevice, getsignalformat, stopdevice, near the VI device

  Best regards

  Thijs Boeree

  Found!

  I only 'open' the device in my VI and then tried to 'stop' it (but it has not been started...) Resulting accidents!

  Best regards

  Thijs

• tables as input for the shared library function

  I played with the call of LV VI using matlab.

  So I built a simple VI which returns an integer as input and multiply it by 10, I then put in a shared library and named it MATLAB - well.

  Now, I tried to do the same thing with a table - I want to send a picture to the VI and multiplied it by 10, but when I build the .h file, it seems that the function expects get table of entry AND exit of table as inputs.

  so, how I can build a shared library VI who gets an array (of a constant size if this is important) and multiply it by 10?

  Thank you!

  A function in a DLL can only return a scalar value, not a table, no matter what languages are used. To return an array, instead calling it allocates the array pass a reference to the DLL and then after the function called the referenced table table contains the new data. This is why there are two parameters - the input array (actually a pointer to it) and a pointer (reference) to the output array. You must change your code in MATLAB, there is nothing you can do about it in LabVIEW. EDIT: Also note that it allows to re-use of the input as an output table, optionally passing a reference only to the table of entry and then by changing that. You can do it in LabVIEW by configuring the setting table as input and output.

• When you call a function in a shared library, are copied locally settings?

  I have a shared library with a function which the header is:

  void __cdecl nextevent (double entry [], int32_t len);

  When it is called it sends the values in [entry] to the input control:

  

  This vi is compiled into a DLL that uses the header above.

  Now, my question is: which of these operations is good:

  1. the input control is a reference to the entry in array [], no value is copied.

  2. the values of the Input [] array are copied into the input control, the local copy is used by the vi, then the values of the local copy is deleted/trimmed.

  It seems reasonable that 1 is good, but I can't be sure, and I see no way to check.

  For this particular case, option 2 is valid. The reason is that the tables of LabVIEW are not just pointers to a memory location but the handles. And there is no legal way to create valid LabVIEW handles of a runtime C allocated memory pointer. If LabVIEW transforms the table pointer entering a handle which is basically nothing else that allocate the handle with a sufficient size to contain all the data in the table and then copy the data from the table pointer in this handle. After the call, the handle is properly released.

• Get a precise timing in a C++ shared library in VxWorks

  Hello world

  I am developing a shared library for VxWorks for my compactRio access a «no massive strorage» usb device

  I work with gcc (see develop shared libraries for the cRIO-901 x and other targets of VxWorks for more details).

  The usb part works fine, but I now have to obtain a precise timing in one c++ shared library functions. I tried the functions clockLib (e.g. clock_gettime () - see page 8 of the http://www-ad.fnal.gov/controls/micro_p/manuals/vxworks_application_api_reference_6.6.pdf for more details), but they seem to have a resolution of 1 ms, which is not enough for me.

  There is a clock source faster on the cRio (at least 1 Mhz, one used for timed loops) but I do not know if such a source could be used in a shared library. If so, anyone knows what are the functions of call?

  Thank you very much

  Martin

  OK, I thought about it.  These functions are exported as C functions, so you should use extern 'C' instead of extern just by itself, as I did originally.  Once I did, I was able to compile the following code in its own. File AND it works fine:

  #include
  extern 'C' unsigned long niTimestamp32();

  extern 'C' Sub TimeTest()
  {
  unsigned long ts = niTimestamp32();
  printf ("niTimestamp32 () = 0x%08X\n", ts ");
  }

  Good luck and let me know if you have any problems and more.

• Unable to load the shared library LVASPT_WA.*

  Hello

  I have a hope that easy to fix the error: I want to use the function "WA Detrend' to the signal processing tool advanced in a real-time application running on a cRio 9030. When I try to run the VI I get the following error:

  ...

  Deployment NI_AdvSigProcWA.lvlib:WA decimation Filter.vi

  NI_AdvSigProcWA.lvlib:WA decimation Filter.vi loaded with errors on the target and was closed.
  LabVIEW: Unable to load the shared library LVASPT_WA.*ptDecimationFilterH:C. make sure that the library is present on the target of RT. Either MAX allows you to install software from OR or FTP to transfer custom RT target libraries.

  ...

  I reinstalled signals Advanced processing toolkit and linked things 'add new software' MAX, but the error persists.

  A picture of what the system looks like to the MAX is attached.

  Also, I Fund this post:

  http://forums.NI.com/T5/LabVIEW/problem-error-deploying-item-on-RT/m-p/3201345/highlight/true#M92822...

  could someone tell me what he means by "Please check the installation of the custom software all mode '?

  Can you telll me what I am doing wrong?

  Thank you very much in advance!

  I ran your situation in R & D, and the problem seems to be as a result of Advanced Signal Processing Toolkit is not not compatible on the x 64 under Linux RT OS in the 9030.  The product page could be clearer on this gap.  I am currently a web application to get this fixed!

  Best,

  David

• Create a shared library for NI Linux real-time

  I need to build a shared library for NI Linux time real (.so) which corresponds to a shared library, which I create on Windows (.dll).

  I have the C code that needs to call a function of VI. On Windows, I have a project that allows me to create and build a "Shared Library (DLL)", but I don't see the same option available in a real-time project targeting the cRIO-9068. Am I missing something, or is it not still possible?

  Hi Wayne,

  Using LabVIEW VIs in other programming only possible through dll environments. In LabVIEW there are options for creating libraries and source, but these distributions will be accessible in LabVIEW and not in other programming environments.

  Concerning

• Call to a shared library a VI on a target NI Linux RT (cRIO 9068)

  Hi, I wrote a very small shared library (.so) with Eclipse (toolchain 2014), which essentially serves as a wrapper for more complex, but I am having problems with the call go to in LabVIEW RT on a target Linux RT - specifically, the cRIO 9068. First: the library was copied in/usr/lib and ldconfig has been correctly implemented. More important yet, I have also written a C program (using Eclipse as well) that calls the single function currently implemented in the shared library: this works perfectly, both in Eclipse and you connecting directly on the cRIO with a Putty terminal. So I guess the shared library itself is ok and can be called from code/external programs. Now, dating back to LabVIEW (2014 here btw). Here's where things get difficult, I guess. Initially, I had the symptoms listed here--> http://forums.ni.com/t5/LabVIEW/How-to-create-a-c-shared-library-so-for-linux-real-time-for/td-p/302... who prevented me from actually run any code on the target of RT. Then I changed the call library function node: various tutorials suggest to put name_of_library.* in the path text box or the name of library, but unfortunately it doesn't seem to work, so I had to put the name and the extension too. But it still produces the error below ("the name of the function is not found" etc.) So I check the box 'specify path on diagram' and add/usr/lib as a parameter to the node library function call: now the VI can work and is actually transferred to the target of the RT... but the cluster of output error returns error 7, which is a kind of "File not found" error. However, I believe that this error message is misleading: indeed, if I try to debug remotely this library shared under Eclipse, I am actually able to pause it. and when I press the Pause button on the debugger, the goal of RT VI pauses, then continues as soon as I press the Resume button, I'm stuck... I tried searching forums and Google as well, but I have not yet found a solution. Any ideas on what's going on? Moreover, I can add more details if needed.

  Problem solved, it was a bad configuration of the node library function call which prevented the actual library (.so) to be called.

• myRIO can't find my shared library .so

  Hi all

  I have developed a shared .so library to run on a device myRIO. I moved my shared library for the path/usr/lib of the myRIO. When I run the .VI I get this error:

  Deployment RT.viRT.vi loaded with errors on the target and was closed.
  LabVIEW: Unable to load the shared library libsolve.so:solve:C. make sure that the library is present on the target of RT. Either MAX allows you to install software from OR or FTP to transfer custom RT target libraries.

  Any idea? I reinstalled the software on the myRIO but I still have this error (I comproved if the shared library is on the right track with filezilla and Eclipse).

  Thanks in advance

  Well lets try a little more detailed explanation:

  Firstly the soname parameter is a parameter of time to compile/link in the project of the shared library. I don't have a computer with a handy Eclipse installation but it's somewhere in the additional indicators in probably the settings of the linker where to a shared library named libfoo.so.1.3.6 add something like:

  -Wl,-soname,libfoo.so.1
  

  You would then copy the shared library resulting on the linux system.

  cp libfoo.* /usr/local/lib
  

  After that, you must do a few extra things:

  (1) change the access rights for the file, otherwise ldconfig may not recognize it as an executable file and simply ignore it:

• shared library problem MathScript

  I have a shared library of labview created in labview 8.2.1.  This labview dll contains a three functions, having to turn a number of mathscript embeded nodes inside of them.  The reason for their compilation in a shared library dll is because I want to call this dll of labview 7.0.  I have a test program of work created in labview 8.2.1 and labview 7.0.

  The problem I had is that these executables both run ok on my machine development, but when I move them to another machine with only the installed runtimes (7.0 and 8.2.1) labview dll function calls fail to do anything.  No errors appear, so it is very difficult to find where the problem occurs.    I have two different dll called in the example program.  The first dll just manages the file access and has not all the mathscript in bits, but the second, which is the one that I'm really interested in, has the mathscript node.  The memory usage in looking, I see it's the appeal of the file access dll but do not do the mathscript one.

  I have installed an evaluation version of labview 8.2.1 on this laptop with only the runtime, run the program and it works fine.  I think there must be something not in the dll but I don't see anything in the options to add something.  I have the mathscript check box selected in the build option.

  I know there are a number of functions that do not work with just running, but I'm not all there that use my program.

  Does anyone have advice?

  OK, I found the solution to my problem.  It was a problem with the version of the runtime that I used.  Labview CDs development is only a partial performance and include all of the files to run applications full (time to install it on his own).  Go to the website of national instruments, there is a period of standard edition which includes everything you need.  Download and install this version seem to have solved the problem.