Jump to content

Justin Huang

  • Content Count

  • Joined

  • Last visited

About Justin Huang

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi Erwin, Why are the '-c' and '-o' options discarded in the buildCommand section for .o target? If the command to build a target, e.g., tgt.out from input.txt, is ' exe -i input.txt -o a -opta x -optb y -optc z ', where the '-o' option does not mean output, how to map this command to 'ipxact:command, ipxact:flags, and ipxact:targetName, ipxact:dependency'? Does ipxact has assumption that each build command should have -o option which means output, and -c option for dependency? How can I know which option should be remved from ipxact:flags? Thanks, Justin
  2. Hi Erwin, What if we used customized inhouse tool to compile hello.c into hello.s (assembly code) and then generate hello.o from hello.s as shown below. how to describe it in IP-XACT XML? hello.s: hello.c cmd1 flags1 cmd2 flags2 hello.o: hello.s cmd3 flags3 2nd question: if hello.c includes a few headers, e.g., a.h, b.h, ..., should these header files be listed as dependency in IP-XACT XML?
  3. Hi, I'd like to encode the .o/.so buildCommand in IPXACT XML fileSet, such that user can rebuild the .o/.so file from XML. For example, the .o/.so generation command look like this: % g++ -c hello.cpp -o hello.o % g++ hello.o -shared -fPIC -o libhello.so Should I encode XML fileSet like below? <ipxact:fileSet> <ipxact:file> <ipxact:name>hello.cpp</ipxact:name> <ipxact:fileType>cppSource</ipxact:fileType> </ipxact:file> <ipxact:file> <ipxact:name>hello.so</ipxact:name> <ipxact:fileType>s
  • Create New...