FORUM D’ENTRAIDE INFORMATIQUE (FEI)
Site d’assistance et de sécurité informatique

Entraide pour le programmation en général (tous langages).
Règles du forum : Entraide concernant la programmation informatique en général, tous langages : recherche ou correction d'un code ou d'une fonction, aide à la réalisation d'un projet...
Pour la programmation web (HTML, CSS, PHP, MySQL...), il est conseillé de s'orienter dans le forum Webmastering.
Merci de lire et de respecter la charte générale du forum.
  • Avatar du membre
Avatar du membre
par filidns
#186042
Bonjour à tous,

Suite a l’évolution de mon appli sur UI composer de chez Nvidia je souhaite faire un build avec NAnt. Nvidia m'a fournis un fichier build ainsi que des fichiers .include mais depuis ils ont arreté UI composer et donc plus d'assistance...

Je n'y connais rien a NAnt et quand j'essaye de suivre les instructions "help", je reçois l'erreur property has not been set pour useflowfile...

Pour mon projet j'ai un fichier principal en .uip redigé en XLM et un autre servant de "flow file" d'apres ui composer en .uia

voici les codes des deux fichiers servant au build:

le fichier setup.include:
Code : Tout sélectionner
<?xml version="1.0"?>
<project name="Viewer">
<target name="setup">
    <echo>Setting up directory structure...</echo>
 
    <property name="UsingFlow" value="${ flowfile != '' }"/>
 
    <property name="BaseFilePath" value="${ directory::get-current-directory( ) }"  unless="${UsingFlow}"/>
    <property name="BaseFilePath" value="${ path::get-directory-name( flowfile ) }" if=    "${UsingFlow}"/>
    <property name="AbsoluteOutputPath" value="${BaseFilePath}" />
    <property name="OutputFileName" value="${ path::get-file-name( uipfile ) }" />
 
    <if test="${ not UsingFlow}">
        <echo message="No Flow"/>
    </if>
 
    <if test="${UsingFlow}">
        <property name="OutputFileName" value="${ path::get-file-name( flowfile ) }" />
    </if>
</target>
et le fichier viewer.build:
Code : Tout sélectionner
<?xml version="1.0"?>
<project name="Viewer" default="uicpreview">
<!-- The following variables can be used to customize the way this script is executed. They can be configured either by the dropdown of Studio's toolbar or the environment variables in Studio Preferences.
    BUILDFILE : path to this Nant file. This is auto-generated by Studio based on the configuration chosed.
    UIPFILE : path to the UIC Project file.
    MODE : Selected via Preview toolbar. It defines the C++ Build Configuration to executed, either ( Debug, Profile or Release )
    PLATFORM : Selected via Preview toolbar. This defines the platform to preview the exported presentation.
    FLOW : Configured via Studio's environment variable. Points to the location of the .xif file if previewing a Flow file
    PREVIEW : Configured via Studio's environment variable. Alternative application to execute on preview.
-->
<uic:integration xmlns:uic="http://www.nvidia.com">
    <uic:preview>"Build Configurations\Nant\bin\nant" -nologo -f:"%BUILDFILE%" -D:uipfile="%UIPFILE%" -D:mode=%MODE% -D:platform=%PLATFORM% -D:useflowfile="%FLOW%" -D:preview_app="%PREVIEW%"</uic:preview>
    <uic:deploy>"Build Configurations\Nant\bin\nant" uicdeploy -nologo -f:"%BUILDFILE%" -D:uipfile="%UIPFILE%" -D:mode=%MODE% -D:platform=%PLATFORM% -D:useflowfile="%FLOW%"</uic:deploy>
    <uic:property name="PLATFORM" label="Platform" help="Which box do you want to preview on?">
        <uic:value name="PC"  label="PC"/>
        <uic:value name="Vibrante" label="Vibrante"/>
        <uic:value name="Android" label="Android"/>
    </uic:property>
    <uic:property name="MODE" label="Release Mode">
        <uic:value name="Release" label="Release"/>
        <uic:value name="Debug"   label="Debug"/>
    </uic:property>
</uic:integration>
<property name="uicomposerpath" value="${ directory::get-parent-directory( directory::get-parent-directory( project::get-base-directory( ) ) )  }" />
<property name="status"         value="0" />
<!--
    Set default property values if they're not passed in.
    Must do this before calculating what external file(s) to pull in.
-->
<property name="platform"      value="PC"      overwrite="false" />
<property name="mode"          value="release" overwrite="false" />
<property name="varStudioName" value="Studio"  overwrite="false" />
<property name="flowfile" value="${ path::combine( directory::get-current-directory( ), useflowfile ) }" unless="${ useflowfile == '_NULL_' }" />
<property name="flowfile" value=""                                                                       if=    "${ useflowfile == '_NULL_' }" />
 
<!-- Name of the executable viewer that is used for preview -->
<property name="Win32ViewerApp" value="${ 'UICViewerWin32' + mode + '.EXE' }" />
<property name="VibranteViewerApp" value="${ 'ViewerLinux' + mode }" />
 
<!-- For conditioners/viewers that have additional DLL dependencies. -->
<setenv name="PATH" value="${ environment::get-variable( 'PATH' ) };${uicomposerpath}\Studio\Build Configurations\bin"/>
 
<!--
    Bring in external NAnt files. Altogether, these must define
    all main targets, "setup", "deploy", "preview".
-->
<include buildfile="Viewer/setup.include" />
<include buildfile="Viewer/deploy_${platform}.include" />
<include buildfile="Viewer/preview_${platform}.include" />
 
<!-- Defer to targets in external file(s), but using our dependencies. -->
<target
    name="uicsetup"
    description="E.g. ceate output folders, set up extra variables.">
    <call target="setup" />
</target>
<target
    name="uicdeploy" depends="uicsetup"
    description="Copy all require files to necessary destination(s)">
    <call target="deploy" />
</target>
<target
    name="uicpreview" depends="uicdeploy"
    description="Kick off the appropriate preview application.">
    <call target="preview" />
</target>
Que dois-je remplacer dans les fichiers exemple pour faire un build?...

Merci pour votre aide!!!
Long-distance relationship

Hello everyone! Lately I have been thinking abou[…]

I appreciate you sharing this knowledge. I adore y[…]

Your information is effective and extremely helpfu[…]

Poppy playtime unblocked is one of the most wel[…]