Re: [Open-discuss] How to build native target project without errors ?

Jean-Charles Gibier wrote:
> Hello,
> 
> For a few months I have tried to build project HELIX (not at full-time obviously :) and I am a little tired. 
> Sometimes build targets lead of, sometimes others not ...
> For instance I can build server 'dist_all' in non static version but in other hand can't build the basic player.
> (In fact some attempts succeed with modified sources but I'd rather not follow this way :-)
> 
> 
> A last example of my desperate quest :
> 
> --------------------------------8<------------------------------------------------------
> Création de la bibliothèque rel32\hlxserverplus.lib et de l'objet rel32\hlxserverplus.exp
> syslib.lib(stataccs.obj) : error LNK2019: symbole externe non rÚsolu "struct DLLMAP const * const g_dllMap" (?g_dllMap@@3QBUDLLMAP@@B) rÚfÚrencÚ dans la fonction "public: virtual int __thiscall Static DLLAccess::Open(char const *)" (?Open@StaticDLLAccess@@UAEHPBD@Z)
> rel32\hlxserverplus.exe : fatal error LNK1120: 1 externes non rÚsolus NMAKE : fatal error U1077: 'link'á: code retour '0x460'
> Stop.
> Time used: 2.99 seconds
> ERROR: WinCompile(server/engine/bin/plus) ERROR: Make failed.
> --------------------------------8<------------------------------------------------------
> Options  are :
> [0] Set BIF branch (SERVER_11_0_STABLE-helix) [1] Set Target(s) (servdistall) [2] Set Profile (C:\source\build\umakepf\helix-server-plus)
> [3] run: build -p green -v -trelease -e -n -c
> --------------------------------8<------------------------------------------------------
> 
> My few questions are :
> 
> Is there any order to build several targets on one fixed branch ?

Different targets should generally be built in different source
trees. Until you are really familiar with the build system you can
get the build files in a state where nothing will work for you.

> Is there any "quick start guide"  to build a native current release target without error message (not a "cookbook" butjust some tips) ?

I work on the client, not the server, but here is the server quick start
guide:

    https://helix-server.helixcommunity.org/2005/devdocs/quickstart

Be sure you have followed and verified the build system setup guide:

    https://common.helixcommunity.org/2004/devdocs/quickstart

> How does the protocol_dist directory is created in Helix tree structure ?

All the _dist directories contain pre-built binary libraries of the
restricted code. This is code that you need to sign an additional license
to get access to. Without that license you compile all of the public
code but link against these distribution libraries to get the functionality
of the restricted code (RA/RV codecs, etc).

These dist-libs are built nightly in our build farms and are checked into
CVS where you can check them out of. You must have signed a binary-EULA
before they will successfully check out (See the build quick start guide above).
You can see if there is dist-libs for your SYSTEM_ID by looking at the
CVS directory:

   cvs -d :ext:[email protected]:/cvsroot/distribution co .

or
    https://helixcommunity.org/plugins/scmcvs/cvsweb.php/?cvsroot=distribution


--greg.


> 
> 
> Thx
> JCG
> 
> _______________________________________________
> Open-discuss mailing list
> [email protected]
> http://lists.helixcommunity.org/mailman/listinfo/open-discuss
> 

_______________________________________________
Open-discuss mailing list
[email protected]
http://lists.helixcommunity.org/mailman/listinfo/open-discuss