Packaging of the project libraries programmatically

Similar Questions

• I can not package for the project when I used the blackberry resource files

  I can't package the project when I used the blackberry resource files.

  Packaging HelloWorl project
  C:\eclipse\plugins\net.rim.ejde.componentpack5.0.0_5.0.0.25\components\bin\rapc.exe-quiet codename=deliverables\Standard\5.0.0\HelloWorl deliverables\Standard\5.0.0\HelloWorl.rapc-sourceroot=C:\workspace\HelloWorl\.locale_interfaces; C:\workspace\HelloWorl\src; C:\workspace\HelloWorl\res-import=C:\eclipse\plugins\net.rim.ejde.componentpack5.0.0_5.0.0.25\components\lib\net_rim_api.jar C:\workspace\HelloWorl\bin
  Cannot open the C:\workspace\HelloWorl\bin/com.helloresL.crb/ dir
  Error! : error: auditor failed: C:\eclipse\plugins\net.rim.ejde.componentpack5.0.0_5.0.0.25\components\bin\preverify.exe d C:\DOCUME...
  Packaging project HelloWorl failed (taken in 0,219 seconds)

  I have fixed my problems, I was using a unicode language in windows, so I changed the language for non-unicode format.

• How to find the path to the project file programmatically

  I'm trying to find a way to get the path to the project file in the development environment.

  I have attached a small project in LV 8.5.1 with a project file, a library file and the VI. I can get the path to the file library, but not to the project. This channel is still .

  I know that the problem exists in LV 8.6.1f1 but I didn't test in LV 2009.

  I am aware that in reality he could there have more nested levels of the library files, but it doesn't matter when this simple example does not work.

  If this is related to the problem I initially created the library by using the file > new... and later, I created the project and added to the library.

  Hi Waldemar,

  Here is a small piece of code and a related link.

  http://forums.NI.com/NI/board/message?board.ID=170&message.ID=220269&requireLogin=false

  I hope this helps.

  Kind regards

  N. Ralf

  Engineering applications

  OR Germany

  PS: Don't forget the congratulations. )))))

• Are there disadvantages to the use of libraries in the project to organize common code used by different projects?

  My company is trying to determine how best to organize and share our common code. We use subVersion. We have several important programs that are deployed on different machines, some of which are running older versions of labview. I read a lot of documents on how to share the code, but I still don't know if it makes sense to use the project libraries to organize the code which will be shared by several projects. Another option is the package build. Can someone comment on the advantages and disadvantages? Thank you.

  Because you use several versions of LabVIEW, go with the packages.

  The project libraries are stored in a specific version of LabVIEW.  So if someone registers in 2014, you can't use it in 2013.

  If you use packet, then you have a core library that is 'installed' for a specific version of LabVIEW.  Each version of LabVIEW can have its own installation of this package.

• Projects and project libraries

  I have luckily been using projects since their introduction in LabVIEW 8 - something.

  I have a project whose job is to look at the trees of directories containing the other screws in some cases, screw my code reviews have the same name as a screws used in the code (I am slot in development, not of an executable Mode).  To avoid "name conflicts", I did a search on and learned namespaces on the project libraries.

  So I have brought successfully on all the files in my project in a project the same library name.  The code works fine.

  Today, I opened my project to watch one of my screws, and to my horror, the project had No files showing.  He also did not show the library project (where I "knew" all the files are located).  A little worried, I looked on my drive and found the project library file (.lvlib) - if I double-click on it, there are my files!

  What I do have trouble (maybe because it's impossible!) becomes an 'inside' view of my library of Project Explorer project.  In view of the close relationship between the projects and the project libraries (the second is created from the beginning, for example), I expected to see such a link.  Are there?  Or are you expected to open both a project (which, in my case, has files that are not in the project library) and the corresponding project library?

  Note that I did a search in the Documentation OR on the project libraries, and what I've read has pointed out the close relationship between a project and an associated project library, including giving them the same (or similar) name and now the files in the same folders.  [Hmm - I just realized I did not name my project and the library identically - I called the project "Project XYZ" and the "Library XYZ" library project...].

  Experience "on the ground" would be welcome!

  Bob Schor

  The library project is just an xml file containing links to all of the objects that make up the project. A .lvlib is also an XML file that contains links to the objects he owns. Screws are marked as belonging to a library. They do not belong to the project. If the .lvlib is included in the project, you will be able to expand to see the items it contains. You don't need to have a project to create a .lvlib. You can create a file/new in the getting started window. You can drag any .lvlib in a project as you can a VI. You shouldn't screw that contains a .lvlib existing in the Project Explorer. Also remember that the .lvlib contains no screws or other objects. If you open it in Notepad, you will see a list of objects.

  What probably happened, is that you did not save the .lvproj after creating and adding the .lvlib. All you would have to do is find the .lvlib in Windows Explorer and drag it to your project.

• Libraries in the project tree

  I recently noticed that some of my projects have libraries added in a separate the 'library' of the project tree branch, while in others they are simply registered at the level of the base tree; see these two examples:

          

  There is a practical difference between these two provisions, in addition to aesthetics? Can I get in trouble in the second? I'm actually in many of my projects in the second scenario without apparent problems, so I tend to answer 'no', but who knows?

  Hello Roberto,

  The hierarchy of the project tree is only to logically organize your files. However, there is no impact on the operation of the program.

  You can change the hierarchy to organize your files in the virtual folder that you want.

  Starting with 2013 CVI, you can also add subfolders, which was not possible in 2012.

  Constantine.

• Eclipse fails to package the project every other time I try to run BlackBerry Simulator

  I have a simple project that I've set up using the SDK 7.1 BlackBerry, it has no external dependencies.

  Almost without fail, every other time I hit him "run on BlackBerry Simulator' I get an error similar to the following:

  Packaging project BlackBerryApplication
  C:\Eclipse\plugins\net.rim.ejde.componentpack7.1.0_7.1.0.10\components\bin\rapc.exe -convertpng -quiet codename=deliverables\Standard\7.1.0\BlackBerryApplication -sourceroot=D:\Git\BlackBerry Application\BlackBerryApplication\src;D:\Git\BlackBerry Application\BlackBerryApplication\res;D:\Git\BlackBerry Application\BlackBerryApplication -import=C:\Eclipse\plugins\net.rim.ejde.componentpack7.1.0_7.1.0.10\components\lib\net_rim_api.jar deliverables\Standard\7.1.0\BlackBerryApplication.rapc D:\Git\BlackBerry Application\BlackBerryApplication\bin
  JAR file creation failed with error -1
  The preverified classes if any are in tmp28761. See jar log of errors in C:\Users\t_gibson\AppData\Local\Temp\rapc_71af6d24.dir\jarlog.txt
  Error!: Error: preverifier failed: C:\Eclipse\plugins\net.rim.ejde.componentpack7.1.0_7.1.0.10\components\bin\preverify.exe -d C:\Users\ ...
  Packaging project BlackBerryApplication failed (took 0.584 seconds)
  

  No matter if I clean up project or own Simulator I still get the same error another each compilation. Does anyone have an idea what could cause this? If I type "run on a BlackBerry Simulator" right after the error, it works fine.

  I use the 9900 with Eclipse 3.7.2 and BlackBerry 7.1.0.10 SDK Simulator. The plug-in version is 2.0.0.201207181003.

  Thank you!

  EDIT: I should clarify that when I say that the cleanup project makes no difference, what I mean is that cleaning of the project once the means it compiles OK next time, but unless he is cleaned after the first compilation, again a second time the compilation will fail. If although the project before each compilation of cleaning could cause it to compile every time, this does not solve the problem that it is there always something left in an inconsistent state after a successful compilation.

  I have determined that the source of the problem was a bad setting in the project configuration that I did when I created the project, I added wrong file the project root to the source compilation path option on folders. The error in the line of rapc.exe is highlighted below

  Packaging project BlackBerryApplication
  C:\Eclipse\plugins\net.rim.ejde.componentpack7.1.0_7.1.0.10\components\bin\rapc.exe -convertpng -quiet codename=deliverables\Standard\7.1.0\BlackBerryApplication -sourceroot=D:\Git\BlackBerry Application\BlackBerryApplication\src;D:\Git\BlackBerry Application\BlackBerryApplication\res;D:\Git\BlackBerry Application\BlackBerryApplication -import=C:\Eclipse\plugins\net.rim.ejde.componentpack7.1.0_7.1.0.10\components\lib\net_rim_api.jar deliverables\Standard\7.1.0\BlackBerryApplication.rapc D:\Git\BlackBerry Application\BlackBerryApplication\bin
  JAR file creation failed with error -1
  The preverified classes if any are in tmp28761. See jar log of errors in C:\Users\t_gibson\AppData\Local\Temp\rapc_71af6d24.dir\jarlog.txt
  Error!: Error: preverifier failed: C:\Eclipse\plugins\net.rim.ejde.componentpack7.1.0_7.1.0.10\components\bin\preverify.exe -d C:\Users\ ...
  Packaging project BlackBerryApplication failed (took 0.584 seconds)
  

• InDesign, address book files, place objects, package the project

  I want to use a book file to combine several smaller files (let's call them "chapters").

  Each of my chapters has a number of objects (cmd - D).

  I said who placed objects remain outside the main .indd file and allow re-binder if one of these files is updated or replaced.

  I use the package tool menu to combine all the fonts placed objects and .indd (and PDF) file in one folder.

  I want to know how to use the objects placed in the chapters that are contained in a book file, and how to package everything when I'm done.

  Where each of the files belong (in which folder); and how they are organized when I pack them?

  How to make a copy of all of the compressed file, to start working on a new iteration [review] the entire book?

  I watched the tutorials and read what I can find.

  I can't find answers to how working together package, the book and the place .

  Thank you.

  • So you place graphics and text files in an InDesign doc (we'll call it aCHAPTERc) and use the features of InDesign to arrange a nice layout.
  • Repeat this process for each chapter.
  • Collect all of the chapters in a book for the paging file, generate a Table of contents, may be a clue.

  Now what? If you want to print, you can export the book to PDF and send it out for professional printing. Or you can package the book (use the menu of the control panel in the upper right of the book panel) and collect everything you need for printing through InDesign in a single project file, as well as folders nested for fonts and graphics. The zip file and send it out for professional printing.

  These days, providing a high-resolution PDF is more common. So, why use the package? Let's say you're not particularly organized. (I am and always start with a project folder and subfolders and put everything that relates to this project in these folders.) But let's say you're not. You can still use the package afterwards, just to collect and copy all of the assets of the project in a new folder (assets include book and chapter files, fonts, graphics and .idml file and a .pdf print quality). Zip, archive and you are ready, when someone says: "Hey, can I get a copy of this article moved you 10 years ago? What is happening to me more that you would think!

• How to debug a project in netbeans without the deployment of the project every time

  Howdy,
  
  No idea how to debug JavaFX projects in netbeans without making every attempt?
  I have a < target name = "- post - jfx - deploy" > ant target just to build the distributable, but he gets run even if I'm just under the project in debug mode, which slows down a lot of things.
  
  Thank you!

  You can configure the standard NetBeans Java project (as opposed to a NetBeans JavaFX project) and specify the jfxrt.jar library in your classpath. You will lose all the support project packing NetBeans provides. However NetBeans take time trying to package (and possibly other undesirable tasks) during development.

  You may also have a separate project of JavaFX (NetBeans project or just an ant or maven build) that you use to build and test your final deployment packages when you need that.

  Note that the development in the intellij idea is similar in that you just put jfxrt.jar in your project libraries, and you can easily develop and debug applications quickly javafx without a need for a step in creating the separate jar which imposes JavaFX NetBeans for a project.

• Cannot open the project on final cut pro :(

  Hey guys, I have a big problem.
  I edited a video which is about 1h30m and using the function "Multicam clip", and successfully made and made a DVD. but unfortunately I need the second edition. Then I opened the library file, click the project, Final Cut Pro X continuous loading and close unexpectedly, and another project to another event works normally. anyone with the same problem? I need to send it to my tmr customer

  p.s. I deleted the file, preferably according to most of the Q & A.

  What version of FCP are you running? If it's the 10.1 or later, projects are in the events that are contained in libraries.

  If 10.1 or later, is the DVD project that does not open in the same library as the project is open? Or they in different libraries

  Russ

• Crashing when you try to access the projects

  Running OS X El Capitan

  10.11.4 version

  iMovie Version 10.1.1

  Whenever I try to refer to projects to modify / change / update of previous iMovie projects will "quit unexpectedly" and I am unable to do anything other than create projects currently. Any help on fixing this problem is greatly appreciated!

  Are the projects that iMovie cause to leave all in the same library? Are new projects that you create in the library as well as those that iMovie cause to quit smoking? How many projects is causing this problem. There may be a corruption of library or a corruption of project based on the answer to my questions. Finally you have several libraries where all is well?

• prototype of the project file information

  I have a request where I build a dll and the functions in the dll must be packaged for use in other software. I am creating the function wrapper for text file automatically. Ideally I ould like to use only the file of the project to do, but there is some information that I don't see in the file.

  I don't see where the prototype of the function. For this reason, I tried to build to the VIProtoInfo I can get all the parameter names, if they are controls or indicators and can determine is that they are chains, but I do not see the data type of other types of controls. I also don't see a way to determine what source for what vi. I know that I could open the screw ' and align stuff but I'm hoping for a cleaner solution.

  Is there a documentation available that could help me to find out this information?

  When you build the DLL, it will also produce a .h header file that contains the function prototypes of the functions in the DLL. Look at the photo 'exit for build specification' - you will see the generated files: http://digital.ni.com/public.nsf/allkb/A3804F88FCDB1E6286257CE00043C1A7

• Do a right click in the Project Explorer is sometimes slow

  I have a big project of the AF with a lot of classes and libraries. I only really use these two (lvclass and lvlib) to structure and organize the project. Right click on VI sometimes takes a terribly long time to load, say up to 10 seconds, depending on the library/class. It appears to be vaguely related to how many things the owners have libraries/classes. What exactly is causing this loading time? Any ideas how I could get rid of this significant disadvantage?

  Here is more information and a few thoughts:

  • Windows 8.1
  • LabVIEW 2015 / 32 bit (I can't say for sure, but I think that I had no such problem on earlier versions 2014 and 2013)
  • Mass of compilation of all of the project (taken as 2 hours) had no effect

  Thanks for all the ideas and resources. I'm very, very happy to announce that this particular fix https://decibel.ni.com/content/docs/DOC-44159 (fix for the issue of AF project provider performance) made my problem disappear. Time has been reduced from ~ 7 sec less than a half second. Wonderful! That, to me, proves false the idea that the mere fact of having hundreds of classes or a large AF would make your current IDE experience terrible.

• 'Clone' of the project library (.lvlib)

  We have a study on sound localization - move us a speaker with a robotic arm, play sound through the speaker, ask our subjects to point a laser where they perceive the location of the sound and press a button.  We can also turn on LEDs and lasers, adjust sync settings, even to move the sound source.  The various tests are "programmed" by entries into an Excel workbook with columns for the timing, healthy situation, sound settings, etc.  In addition to the Excel workbook, we generate 3 output files - a header file XML that describes the configuration of the recording (analog and digital channel names and scales) and saves the settings of each trial as it is executed, an XML event which records all of the events of "point-in-time", such as Messages, status changes, or modifies the digital I/o, and a file of examples that contains N (usually 16) sampled analog and digital channels sampled at 1 kHz.  We control all of this a LabVIEW Real-time project, which also includes routines to study, manipulate and analyze data of output files.

  The project evolves (slowly) - we are currently at Version 2.0 (Version 1.x was developed in LabVIEW 7.0, this is the complete rewrite 2012/2014, "start from scratch and do it right, or at least better").  We are contemplating adding the ability to study the sounds delivered via stereo headphones (vary the volume from left to right or by adding a small time gap between channels) and calls this Version 2.1.

  To try and prevent "Version hell", we intend to do "backward compatibility" Versions - we will Add some new columns to the workbook Excel for new parameters in headphones, but put in place LabVIEW code to simply "do nothing" (with headphones) if he reads a Version 2.0 workbook where these parameters are lacking.  This allows us to code of Version 2.1 allows to make a Version 2.0 experience.

  We are faced with one of the problems are to know how read and analyze or manipulate data files resulting.  For example, the header file contains specific sets the version of the data, which are analyzed by the XML parser and converted directly into a Cluster of LabVIEW.  Thus a Version 2.0 file must be read by the code who "knows" a Cluster of Trial Version 2.0, whereas a 2.1 file needs a trial 2.1 Cluster.

  When I read the header file, the first thing I encounter is the Version number (2.0 or 2.1).  Knowing this, I could, in principle, use a Case statement to call a Version 2.0 or Version 2.1 analysis routine.  But I am trying to 'avoid a mess', and libraries in the project seems a good way to do so, if I understand how to use them properly.

  [For now, I have to say that I tried a little experiment: I have created a new project, built Library1 in a folder with a 'Hello' and 'Test' Library1, built the library 2 (inside the folder library 2) with 'Hello' and 'Test' (different) and called the high-level.]  Worked well.  I then "took a shortcut" and copied the folder Library1 (outside of LabVIEW) on the menaces3.  When I said that the project to add 3 library, I had a mess of conflicts, which I couldn't resolve.  And I "broke" LabVIEW - even after removing all the .lvlib and the .lvproj files, I couldn't create a project and make a folder to add (Snapshot) without a missing file error to appear.  I did the experiment using LabVIEW 2012 - this problem has affected not only LabVIEW 2012, but also 2013 LabVIEW and LabVIEW 2014, but not LabVIEW 2011.  I spoke with the support of OR, which are also puzzled.  I am currently working in a new virtual machine until I can get LabVIEW "repaired"].

  What I want to do is identify all Version-specific routines in my folder of analysis and include data in this case TypeDefs for the Version-specific parts.  I would then "wrap" all this in a project library Version 2.0.  The code "on the outside" would have its own copy of TypeDefs (she could use the "Latest Version", as external routines are supposed to be 'backward compatibility'.

  So here are my questions.

  1. Suppose that I restructured my project so that I have a record, both "Real" and "Virtual" (in the project) parsing, and it contains a subfolder called Version 2.0 that contains the Version-specific TypeDefs and most of parsing code.  Is there an easy way to transform the Version 2.0 to Version 2.0 Library folder so that when I call functions in this library, they use Version 2.0 of the TypeDefs of the library, regardless of the TypeDefs declared in the main routine?
  
  
• Assuming that I have a folder of Version 2.0 of work and the library, is there an easy way to "clone" to make a folder of Version 2.1 and the library?  If so, all I would need to do the "work" for Version 2.1 of the code would replace TypeDefs of Version 2.0 in the file of Version 2.1 with the "correct" TypeDefs, and (b) add any additional analysis code is required for the new features in the new Version.

I apologize for the long-winded nature of this issue.  I look for tutorials on libraries of the project (there are), but none covered this topic.  To pay for your patience, I am happy to write and submit to the OR for a future white paper on libraries of the project - which would speak?

Bob Schor

PS - Moderator - if it belongs to another Forum, feel free to move it.

On the money Bob!  Save under... Duplicate the hierarchy to the new location (requires that the new library offers a new name)

To convert a virtual folder to a lvlib just to create a new lvlib in the project and move the project members want in the new lvlib Project Explorer does the rest of the book nitty gritty on registration of the members of the lvlib with the new property information.  (You will be prompted to save the members when the composition is changed)

And Yes, it's the kind of mistake you don't do twice.  And, believe it or not, I had this type of issue used to justify not using projects! "they are too much hassle when you mud round in windows Explorer ' then I asked them if the never borrowed the car of their father and did not him tell you parked above on the next Street.  They now use projects.

• VI to determine the name of the project

  For a real-time application, I wanted to determine, at runtime, the name of the project in which the VI has been "content".  I wanted to get the name of the project (even) under four different conditions:

  • on the host, in development mode
  • on the host, in Run-Time mode (i.e. after being built as an executable)
  • on the goal of RT, development mode
  • on the aim of RT, in run mode.

  It is not so easy.  I figured out how to make the first two (use the name property of the active project development and use the next last folder directory of the Application in Run-Time mode mode), but I'm having trouble to get this information to get the target RT code.  Has anyone tried this before?  Did you?  Advice (or even downright Solutions)?

  Bob Schor

  Well, I figured out, but it's not pretty.  In the previous post, I explained why I wanted to do - here I will explain how I did this.

  There are three main modes, under which Applications can run: development mode (when you are programming in LabVIEW and press the button "Run"), Run Time System (an executable on a PC) and Embedded (code that runs on a target in real time, in the form of executable file or development).  Of these, only one mode of development gives you access live (via the Application, the active project property) in the name of the project file.  My goal is to have the user interface and the RT 'chunks' of the project in real time have access on behalf of the project, the system I'll create will use same code on two subsystems, meaning that it will run on the PC at least once in the mode of development .

  The key step is to create a 'constant VI', I'll call CONST name of the project, which consists of a single indicator of string, name of the project, which "held" the name of the project.  I initially thought to use a Global Variable, but there is a technical problem with that I will mention later.  I didn't use CONST name of the project directly, but, instead, use a 'Get the project name' VI that has, for its single release, the name of the project.

  This VI, when it runs, determines the type of request under which it is running.  If it is something other than the Mode of development, he calls CONST project name and returns its value.  If this is the Mode of development, it gets the name of the project, he returned, but just before leaving, he arranges to be updated programmatically CONST project name when it is called in the future, it will return the name of the project (update).  [Then why not simply initialize CONST project name?  I'm looking for a "generic" solution that will always return the correct value, even if I move to another project and don't remember about the change and change - all I have to do to make it work is to run once in the mode of development.  Who has ever developing code without testing before making the executable?].

  I wrote a VI gave the name of project Save, which does the following: he calls set the timer on CONST project name to define the name of the new project (this works even if we put an indicator), calls to use current default to make the new value "stick" and called "Instrument to save" to save the changes.  The problem is that CONST project name cannot be "running" in the State to use current default work without raising an error.  If the name of the Save project is simply called as a Subvi to get a project name, it will be in the State of operation as it is used in the case of non-development mode to get a project name.  The solution to this witch hunt is to use the asynchronous call with-and-Forget 'spawn' name of the Save project.  Finally, we modify register project name so that it starts with a loop "wait", examinging the State of execution of CONST name project and waiting for it to exit the executing State, indicating that it is prudent to make the change.

  Phew!  But it works!  Oddly enough, when I tried this using a Global Variable instead of my Constant VI, I kept getting errors during execution are currently lacking, but despite the mistakes, the code seemed to run correctly.  I found an article (written for LabVIEW 5!) explaining that it was expected as Globals behavior were always in the State of operation.  Actually, I just realized that I had not tried with the call-and-Forget asynchronous schema, then perhaps a decade later, LabVIEW will allow me to do this using a Global without raising an error...

  BS