WMP Shared Library work

Similar Questions

• 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

• 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.

• 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.

• 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.

• import the shared library function name change

  Hello

  I used 'Import Shared Library' to create a lvlib, but he changed function name, for example to Z2onj() on(), so created VI does not work.

  It has this error:

  Call library function node "libname.": Z2onj: function not found in the library

  Details:

  The name of the function specified for this node is not found in the library. Click the node to call a library function and select Configure, and then choose the name to function properly.

  How can I solve?

  Thank you.

  Hi Salvo,

  you need to create again the lvlib with the new name.

  Kind regards.

• Is Linux - possible to build a shared library that calls other libraries shared without having to make a static link to them?

  Hello

  Operating system = Linux (Ubuntu 14.04 LTS 32-bit)

  I am building a shared library *. so.  This *.so should be used by LabVIEW.  This *.so is calling other functions in shared libraries.  In my case, the other library share is libxml2 and libz.  The only way I could compile my shared library and operate was a static link from libxml2.a and libz.a.  Is there a way to make a dynamic link?

  Here's the makefile file that I use.  The goal of 'TestValidateSchema' compiles the shared without the static link library and this shared library is called by an application to test 'c' and it works.  Now, to make it work in LabVIEW, I need to make a static link, as you can see in the target ' install: «otherwise the function "call library node" throws me a symbol unresolve...»»

  This is the only way to do it and if yes why?

  Thank you

  --------------------------------

  CC = gcc

  all: TestValidateSchema

  TestValidateSchema: testValidateSchema.c
  $(CC) o Release/validateschema.o - c - wall - Werror - fpic Src / validateschema.c - I. / Include-I/usr/include/libxml2
  $(CC) - shared-o./Release/libvalidateschema.so./Release/validateschema.o
  $(CC) - wall o ./release/testvalidateschema testValidateSchema.c./Release/validateschema.o-lxml2

  clean:
  $(RM) $(OBJS)./Release/testvalidateschema./Release/libvalidateschema.so./Release/validateschema.o /usr/include/validateschema.h /usr/lib/libvalidateschema.so

  install:
  $(CC) o Release/validateschema.o - c - wall - Werror - fpic Src / validateschema.c - I. / Include-I/usr/include/libxml2
  $(CC) - shared-o./Release/libvalidateschema.so./Release/validateschema.o Src/libxml2.a Src/libz.a

  --------------------------------------

  In addition to what said Daniel on the specification of an external shared library in the liaison stage of your version of the shared library, together with the - shared option, there is still one thing to consider:

  Your library of hello.so then contains references to functions in external shared libraries libxml.so and zlib.so. When LabVIEW calls dlopen ("/ path/dir/hello.so",...) it basically hands of any control in the linker Linux running, ld.so that takes care of the rest. LD.so then try to load the shared library, recognizing that there are external references and try to solve.

  First he tries to match the missing external references to any symbols that have been previously loaded into the current process already. If this is not successful for a particular system, it queries the ldcache for a library and a symbol. ldcache is updated with the ldconfig program. When you add a new shared library on the system that you want the linker ld.so runtime in order to find, run ldconfig.

  NOTE: Running ldconfig is not normally necessary to shared libraries that access you directly via the node call library, as you specify here the full access to your custom library shared already, so path ld.so will fail immediately if it is not the library specified in the given absolute position and will not attempt to query ldcache at all.

  If you are installing packages through your package manager platform update ldcache for all publicly accessible libraries shared in these packages is usually done automatically for you as part of the package installation script. If however you manually install the libraries you need to run ldconfig yourself. In your case, you could add the libxml.so and/usr/lib zlib.so and simply run ldconfig from the command-line as it default search/lib and/usr/lib for libraries shared and rebuilt the ldcache from that. If you add your new libraries in a different directory on your computer you need to run ldconfig with - n option, saying what directory the new shared libraries have been installed.

• Error during the generation of shared library for OSX

  Hello

  I am trying to build a shared library (.framework) using LabVIEW 2011 as Mac.

  My Version of OSX is 10.7.3.

  When I run the build process, TI allways give up showing the error message:

  There is 1 error in DLL - C compile Source File.vi Possible reason (s): you must have the Apple Developer tools installed to build a shared library. Install the Apple Developer tools and attempts to reconstruct the shared library.

  I don't know what developer tool is missing or if there is another problem with my environment.

  Thank you

  Gschwert

  Hi Gschwert,

  in the meantime, I received a response from our developers in Austin.

  Developer Tools Apple which refers to should be X-Code.

  They work with X-Code Version 3.0 and have no problem. They will try to work with your versions (4.2 and 4.3) too and take a look, if there is something special to look for.

  Have you tried using X-Code 3.0? Then you get the same problems?

  Good day

• Error message "unable to load the shared library.

  I try to get my programs for school to work, and I get these error message whenever I try to run anything. The last line of the State of deployment is as follows:

  Deployment time get NLVSim and isAcceptedStep.vi IsAcceptedStep.vi and NILVSim get busy with errors on the target and has been closed.

  LabVIEW: Unable to load the shared library NILVSim.*: SIM_GetTimeAndIsAccepted:C. make sure 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 tried everything I can think of to fix this. I checked NEITHER Max and I'm all for date on the software. I reinstalled LabVIEW twice, and I reset my myRIO. My classmates do not experience problems with getting theres to work. I start to lose hope and hope someone might know what the question. Thank you for your help.

  WubaDee,

  NILVSim is part of the LV Control Design and Simulation Module. This one is correctly installed on your Windows development system and you installed it on your myRIO?

  Norbert

• Shared library with 10.2 NDK

  I have some classes of Qt/stunts, I'm working on that I want to incorporate a shared library.

  Originally, I was able to follow http://supportforums.blackberry.com/t5/Native-Development-Knowledge/How-to-create-a-shared-or-static... to create the library, but in the latest releases of the NDK, this does not work.

  Method B of this article does not work for Qt\Cascades classes since moc is never called, even if the used compiler is QCC. If I want to do a project of Qt\Cascades, I can only do an application project. If I tape everything that is not related to the library (assets, translations, master, etc.). I got some errors.

  Is first with the missing translation files. This can be corrected by changing the make files and the file *.pri (although I guess it will be readded by the NDK...)

  The second and more important question, is that even when I add "TEMPLATE = lib" in the file * .pro, which appears to have ignored, I get an error which is described as 'missing main function', which tells me that it is still trying to apply as opposed to a *. so.

  How can I produce a shared Qt\Cascades within the current NDK 10.2 library?

  Discover my stunts/Qt library template https://github.com/blackberry/Cascades-Community-Samples/tree/master/Cascades-Library-Template.

  It should have everything you need.

• Failed to load a shared library

  I'm trying to build and debug an example simple stunts of application (eg. Tabs pane) in Momentics 2.1.1 beta.

  First of all, I had a lot of unaccounted or inclusions synax error I solved all... now, no error in the editor.

  However, while doing a generation clean I get these error in CDT build console.

  F:\bbndk\host_10_3_0_2702\win32\x86\usr\bin\ntoarm-ld: caveat: liblgmon.so.1, need to F:/bbndk/target_10_3_0_698/qnx6/armle-v7/usr/lib/libbbcascades.so, not found (try using - rpath-rpath-link)
  F:\bbndk\host_10_3_0_2702\win32\x86\usr\bin\ntoarm-ld: caveat: libcounters.so.1, need to F:/bbndk/target_10_3_0_698/qnx6/armle-v7/usr/lib/libbbcascades.so, not found (try using - rpath-rpath-link)
  F:\bbndk\host_10_3_0_2702\win32\x86\usr\bin\ntoarm-ld: caveat: libforensics.so.1, need to F:/bbndk/target_10_3_0_698/qnx6/armle-v7/usr/lib/libbbcascades.so, not found (try using - rpath-rpath-link)

  It nevertheless compiles and works perfectly if the start mode is run but when debugging is selected as the mode of launch, it throws errors following 4-5 sec apart (sometimes 10 sec).

  On one of the debug consoles.
  WARNING: do not load symbols of shared library for 3 libraries, for example base/lib/liblgmon.so.1.
  Use the command "info launch" to see the complete list.
  You need 'set solib-search-path' or 'set sysroot?
  WARNING: don't load shared library for the proc/boot/img_codec_png.so symbol.
  You need 'set solib-search-path' or 'set sysroot?
  WARNING: don't load shared library for the base/usr/lib/graphics/omap4470/libusc.so symbol.
  You need 'set solib-search-path' or 'set sysroot?
  WARNING: don't load shared library for the base/usr/lib/graphics/omap4470/libsrv_um.so symbol.
  You need 'set solib-search-path' or 'set sysroot?
  WARNING: don't load shared library for the base/usr/lib/graphics/omap4470/libpvr2d.so symbol.
  You need 'set solib-search-path' or 'set sysroot?
  WARNING: don't load shared library for the base/usr/lib/graphics/omap4470/libIMGegl.so symbol.
  You need 'set solib-search-path' or 'set sysroot?
  WARNING: don't load shared library for the base/usr/lib/graphics/omap4470/wsegl-screen.so symbol.
  You need 'set solib-search-path' or 'set sysroot?
  WARNING: don't load shared library for the base/usr/lib/graphics/omap4470/libImgGLESv2.so symbol.
  You need 'set solib-search-path' or 'set sysroot?

  On another console debug

  QML debugging is enabled. Use it only in a safe environment!
  Cascade server was able to start - exit application
  ResourceManager: Window controller has not been initialized by trying to resolve assets.
  Unable to solve "/ main.qml".

  The screen is Virgin throught... and app suspends. If I try to take it back, he just leaves

  Can anyone help please me... if you need more information please let me know.

  8.1 Windows 64 bit

  Momentics 2.1.1 beta

  Blackberry Z10 STL100-1 device

  You can abandon the automatic symbol loading shared libraries. Choose edit configuration, go to the section of debugger, then tab shared libraries. It uncheck the box for "load symbols automatically shared libraries.

• Native extension using the shared library

  Hello

  IAM trying to create an extension which will be used in cordova, well the work of foundations... but what I have to do is add a shared library from another company for my project.

  They have a folder with all the files of all and a .so file, how can I add to my project and use it in the extension?

  Thank you.

  You start with the model BB10-Cordova?

  https://github.com/BlackBerry/WebWorks-community-APIs/tree/master/BB10-Cordova/template

  You should be able to add the library to the project using the Add Library Wizard in project-> generation properties C / C++-> the settings-> the tool parameters

  Note: It is recommended that you back up your project first.

• 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

• How to create a shared library of Qt and use it on App without a head?

  Hi all

  I'm experimenting with some waterfalls headless basic application development, and I just hit another problem of blocking.

  I want to create a Qt library with some shared code between the head and user interface elements.

  That's what I did:

  1. created a new application without head the wizard project
  2. created a new library shared by using the wizard project. Adds a simple C++ (Qt not) class
  3. Set up the two parts of the Headless App to use the shared library ("Library in the workspace project" option from the "Add library...) (' Assistant).   Everything compiles and works very well so far.
  4. Now, I want to use the shared library Qt. I choose 'Library of the Standard BlackBerry platform' and ' platform > Qt Core "from the «add library...» "Wizard. Now, I had this error on the shared library project: C:\dev\bbndk\host_10_2_0_15\win32\x86\usr\bin\ntoarm-ld: could not find lQtCore.

  How to create a shared library of Qt and use it on App without a head?

  In fact, I would also use other NDK libraries on library shared as lbbdata and libbbdevice.

  I expect that workers would deal with all the problems for me. As an improvement, I suggest you add the selection screen platform library of the Wizard "Add library...". «the wizard «Shared Library Project»

  There is a model of library project

  https://github.com/BlackBerry/Cascades-community-samples/tree/master/Cascades-library-template

  Unfortunately, the library create Assistant isn't really useful #t

  There is also a great series on using headless headless library and user interface:

  http://devBlog.BlackBerry.com/2014/02/a-flexible-architecture-for-enterprise-mobile-applications-par...

• Dim in Shared Library is not CustomXTopMember or EnableCustomXAggregation properties

  We are reclassification of 11.1.2.1 to 11.1.2.3.500. We use the shared library for our HFM application. In 11.1.2.3.500, there is no options for EnableCustomXTopMember or EnableCustomXAggregation (where X is the number of the custom dimension IE custom 1, custom 2, 3 Custom, Custom 4).

  In the dimension of local account in the new version, it has these properties.

  In the dimension shared account in the old version, it has these properties.

  In the dimension shared account in the new version, it doesn't have these properties.

  In the new version, I had to copy the application account dimension to get the Dimension Associations to create the shared library, but even with the Dimension Associations created, we still do not see the properties of the shared library.

  We have our custom in the shared library setup of dimensions.

  We have tried to import via LCM and import profiles, but LCM gives us errors and warnings that it cannot associate the property with the dimension:

  "There was an error during the processing of the dimension for the base dimension 'Account' association, dimension target"Custom1 "; Please make sure that the dimension of the target exists or is included in the section of the dimension of the source of imports.  Member of this association properties will not be processed. »

  Any ideas on why the properties not exist in the shared library and will not import or copy in the shared library in 11.1.2.3.500?

  Here are a few screenshots:

  

  

  

  

  Thank you

  Hi Steve,.

  I met the same problem too.

  To work around the problem, start creating a dummy application with dimensions shared new version. This will create associations. After that, you can remove the application.

  See you soon,.

  Thanos