Let's suppose you have a non-axi bus RTL core of verilog or vhdl files, and add them to your vivado project, and sucessfully compile the rtl source files using synthesis and taking care cancel and not run implementation stage.
Now I try to package all the verilog or vhdl into an vivado user IP using the vivado menu:
Tools->Create-and-Package-new-ip
Packaging Options: Package your current project using the project as source for creating a new IP definition
All it does is create a directory with a copy of all by verilog or vhdl source files in a directory with a "component.xml" file.
How to even use this component.xml file???
I create a new project... there's no where to even load the "component.xml" file into vivado so i can find the IP core in the IP integrator menu when making a block design??
I want to create IP cores have them nicely wrapped in separate vivado project, and then import them into a freash new project that contains only a block design. vivado seems to not like this flow... any ideas how to do this?
(I don't know... I just think there's something half-baked about the way this works in vivado...)
I just found out I need additional step for it to be seen in current project:
1. Goto Sources window
2. click Hierachy tab
3. select click IP-XACT->component.xml
4. double click IP-XACT->component.xml
5. scroll to bottom of "Package IP" window
6. click "Re-Package IP" button
7. Now it will show up under: IP Catalog->UserIP->corename
Still not sure how to get this to show up in a new project.
I found out how to import an already created components.xml into a clean project:
In vivado:
1. File->Open-IP-XACT
2. Select components.xml
3. This will open Package IP directory
4. In this window under "Review and Package" scroll to bottom
of Review and package window and click "Package-IP"
Now it will show up under: IP Catalog->UserIP->corename
One would think this would show up under the "+" button for adding "things" to your project... but no... its under File->OPEN-IP-XACT menu.
Related
I have created an app in Xcode and Swift 4 that uses the external frameworks 'SwiftCharts'.
All works fine, however if I move the folder where the whole project and all its files are contained, I get the error message "No such module 'SwiftCharts'" appear after every "import SwiftCharts" in my project.
I need to submit my project as a university assignment but at the moment the only place the project will work is in my Documents folder on my laptop.
You can check the module by Right click the SwiftCharts and check by Show in Finder.
If it is not present in the folder, you need to copy it in the projects.
I would recommend you read about Embedding Private Frameworks in Your Application Bundle:
you normally specify the full path to the appropriate frameworks
directory. When you embed a framework inside a bundle, however, the
location of the framework is not fixed, so you have to use the
#executable_path placeholder to let the framework know its location is
relative to the current executable.
Open an inspector for your framework target and select the Build tab.
Set the value of the Installation Directory build setting to
#executable_path/../Frameworks.
From this link:
https://developer.apple.com/library/content/documentation/MacOSX/Conceptual/BPFrameworks/Tasks/CreatingFrameworks.html#//apple_ref/doc/uid/20002258-106880
Managing external references in any project is essential to understand.
I am trying to use a custom framework in a playground as described in this Apple documentation:
http://help.apple.com/xcode/mac/9.0/#/devc9b33111c
However, I am unable to get the playground to recognize the framework (https://github.com/gk-brown/MarkupKit). It is a 64-bit Objective-C framework that defines a module.
Here is what I have tried:
Create a new "single view" playground
As directed in the document, open the playground and choose File > Save As Workspace
Close the playground
Open the workspace containing the playground
Attempt to choose File > Add Files to [Workspace Name]
The menu item is actually named "Add Files..." and is disabled. I'm able to work around this by opening the Navigator panel and selecting Project Navigator. The menu item changes to "Add Files to TestPlayground" and becomes enabled.
Moving on, as directed in the document:
Navigate to the directory containing the framework, select the framework, and click "Add"
In the editor, open the desired playground source file
Add an import statement for the framework (e.g. "import MarkupKit")
The console displays the following error:
error: TestPlayground.playground:5:8: error: no such module 'MarkupKit'
The document additionally notes that the workspace must contain at least one active scheme that builds a target. However, adding a project to the workspace and building it does not resolve the problem. The playground is still unable to see the framework.
Based on what I've read elsewhere on SO, it seems like this should be possible. However, most of the information I have found is 2-3 years old and may be out of date. The framework is a universal binary, and I have tried trimming it using lipo as suggested in some other posts. Specifically, I did this:
https://github.com/gk-brown/MarkupKit/wiki/Deployment
Unfortunately, it didn't help.
Any suggestions would be very much appreciated.
You steps looks okay but
Only missing part I see here is adding a .swift Empty file in the project.
This actually compiles below project so after this framework will be ready to import into the playground.
I have installed qnx660 in Ubuntu 14.04.
1-I have created a test project hello world for application.In Build variant option i have selected x86 variant. While building the project there is no error message in the console. After building the project in side the work space for x86 its creating both o and o-g folder. But when trying to run project as C/C++ QNX Application some error like "must select a target". So please suggest me how to resolve this issue.
2- I have created two project one for application and second for shared library. From application i want to access API which have to define in the library. But i am not able to write anything because there is no .c file to write. In library project only Makefile and comman.mk is available. So please help me to solve the issue.
Right click on your project.....then Properties -> Qnx c/c++ project -> Build variants TAB. You must check platform and build variant (release or debug) . Please, see image
then open Debug Dialog and choose Qnx target. Press bug image and choose "Open Debug Dialog"
In the Debug dialog choose Main tab and in the bottom you must choose Qnx Target. I attach screenshot.
For your second question.....simply Right click on your progect , then New->Header File (or Source File)
I'm working with a group of friends on a project, and we're doing it in Objective-C++, which I understand is just Objective-C with the ability to use C++ as well.
I'm curious how I'd go about creating a project like one of my friends has setup. They have a main.mm that runs everything important and starts the program up seemingly, where I'm using to the AppDelegate.m serving that purpose.
How do I get a project where it's just a .mm file that serves as the focal point, but still has all the Foundation properties like NSDate and whatnot? I don't want a UI, I just want command line input/output.
In Xcode, create a new project from the "OS X -> Command Line Tool" template and choose
"Type: Foundation". Then rename "main.m" to "main.mm".
In Xcode File > New Project then select Application under OS X. Choose Command Line Tool and press next. Put in a name and make sure Type is set to Foundation.
Then you'll need to rename main.m to main.mm and link against the c++ std library. This answer describes how to add the std lib to the project.
Someone recommends me to use SI to read the c source of PHP ,a great open source project.
I've already downloaded the source.
But I don't know how to import it,can anyone help?
Open the Project menu and create a new project (or push Alt+Shift+N). In the upcoming dialog window, enter PHP as the project's name and select a folder to store the project data. Click OK to configure the project, e.g. activate storing function-local symbols in the project DB etc. Click OK again.
The next dialog lets you actually import files to the project. Select your source folder and click "Add Tree" to add the whole directory structure to the project. Click Close. You can now start browsing the source code.
Make sure you configure SourceInsight so that it knows where your local library folders are, i.e. the C headers & runtime. This is usually done when installing SourceInsight.