How to build native target project without errors ?

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_dllMap3QBUDLLMAPB)
rÚfÚrencÚ dans la fonction "public: virtual int
__thiscall Static DLLAccess::Open(char const *)"
(?OpenStaticDLLAccessUAEHPBDZ)
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 ?
Is there any "quick start guide"  to build a
native current release target without error message (not a
"cookbook" butjust some tips) ?
How does the protocol_dist directory is created in Helix
tree structure ?


Thx
JCG

_______________________________________________
Open-discuss mailing list
Open-discusshelixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/op
en-discuss

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_dllMap3QBUDLLMAPB)
rÚfÚrencÚ dans la fonction "public: virtual int
__thiscall Static DLLAccess::Open(char const *)"
(?OpenStaticDLLAccessUAEHPBDZ)
> 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/devd
ocs/quickstart

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

    https://common.helixcommunity.org/2004/devdocs/quicksta
rt

> 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:your_name_herecvs.helixcommunity.org:/cvsroot/distribution co .

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


--greg.


> 
> 
> Thx
> JCG
> 
> _______________________________________________
> Open-discuss mailing list
> Open-discusshelixcommunity.org
> http://lists.helixcommunity.org/mailman/listinfo/op
en-discuss
> 

_______________________________________________
Open-discuss mailing list
Open-discusshelixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/op
en-discuss

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_dllMap3QBUDLLMAPB)
rÚfÚrencÚ dans la fonction "public: virtual int
__thiscall Static DLLAccess::Open(char const *)"
(?OpenStaticDLLAccessUAEHPBDZ)
> 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/devd
ocs/quickstart

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

    https://common.helixcommunity.org/2004/devdocs/quicksta
rt

> 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:your_name_herecvs.helixcommunity.org:/cvsroot/distribution co .

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


--greg.


> 
> 
> Thx
> JCG
> 
> _______________________________________________
> Open-discuss mailing list
> Open-discusshelixcommunity.org
> http://lists.helixcommunity.org/mailman/listinfo/op
en-discuss
> 

_______________________________________________
Open-discuss mailing list
Open-discusshelixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/op
en-discuss

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_dllMap3QBUDLLMAPB)
rÚfÚrencÚ dans la fonction "public: virtual int
__thiscall Static DLLAccess::Open(char const *)"
(?OpenStaticDLLAccessUAEHPBDZ)
> 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<-----------------------
-------------------------------
> 
This is not a correct BIF branch. The correct branch for
11.0 is
SERVER_11_0_STABLE (not '-helix').

Be sure to read the server build guide here
https://helix-server.helixcommunity.org/2005/devd
ocs/quickstart
and choose an appropriate branch and SYSTEM_ID as described.
Also as Greg pointed out, you cannot build different
branches,
profiles, or system IDs in the same directory.

> My few questions are :
> 
> Is there any order to build several targets on one
fixed branch ?
There are aggregate targets and installers. In your case I
imagine you
probably want to build the installer.

> Is there any "quick start guide"  to build
a native current release target without error message (not a
"cookbook" butjust some tips) ?
There is the build guide (quick start guide) linked above.
Not sure what
you mean by "native" though.

> How does the protocol_dist directory is created in
Helix tree structure ?
This is checked out from the binary distributions directory
based on the
platform ID and profile.

Jamie

> 
> 
> Thx
> JCG
> 
> _______________________________________________
> Open-discuss mailing list
> Open-discusshelixcommunity.org
> http://lists.helixcommunity.org/mailman/listinfo/op
en-discuss

_______________________________________________
Open-discuss mailing list
Open-discusshelixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/op
en-discuss

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_dllMap3QBUDLLMAPB)
rÚfÚrencÚ dans la fonction "public: virtual int
__thiscall Static DLLAccess::Open(char const *)"
(?OpenStaticDLLAccessUAEHPBDZ)
> 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<-----------------------
-------------------------------
> 
This is not a correct BIF branch. The correct branch for
11.0 is
SERVER_11_0_STABLE (not '-helix').

Be sure to read the server build guide here
https://helix-server.helixcommunity.org/2005/devd
ocs/quickstart
and choose an appropriate branch and SYSTEM_ID as described.
Also as Greg pointed out, you cannot build different
branches,
profiles, or system IDs in the same directory.

> My few questions are :
> 
> Is there any order to build several targets on one
fixed branch ?
There are aggregate targets and installers. In your case I
imagine you
probably want to build the installer.

> Is there any "quick start guide"  to build
a native current release target without error message (not a
"cookbook" butjust some tips) ?
There is the build guide (quick start guide) linked above.
Not sure what
you mean by "native" though.

> How does the protocol_dist directory is created in
Helix tree structure ?
This is checked out from the binary distributions directory
based on the
platform ID and profile.

Jamie

> 
> 
> Thx
> JCG
> 
> _______________________________________________
> Open-discuss mailing list
> Open-discusshelixcommunity.org
> http://lists.helixcommunity.org/mailman/listinfo/op
en-discuss

_______________________________________________
Open-discuss mailing list
Open-discusshelixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/op
en-discuss