Re: [mico-devel] Building mico on Cygwin

2006-10-13 Thread Karel Gardas


Hi,

please do not do it! The demos you've copied are for old basic object 
adapter which was already removed from the MICO 2.3.12 release. Please 
rather have a look into bundled examples in demo/poa directory. They are 
counterparts of old BOA demos and should just work.


Cheers,
Karel

On Thu, 12 Oct 2006, Arun Biyani wrote:

I am trying to build  execute the example (client + server in 1 file) from 
the book
Mico An Open Source... by Arno Puder... I copied the directory *boa* into 
mico/demo.

First I had compile errors because iostream.h was not included. I also had to
change Account_skel to Account since account.h did not seem to have a
class called Accout_skel.

After these changes, I got a clean compile  link but then I get error below:

[account$:755] ./account.exe
uncaught MICO exception: IDL:omg.org/CORBA/MARSHAL:1.0 (0, not-completed)
Hangup
[account$:756]

What am I doing wrong?
Arun




--
Karel Gardas  [EMAIL PROTECTED]
ObjectSecurity Ltd.   http://www.objectsecurity.com
___
Mico-devel mailing list
Mico-devel@mico.org
http://www.mico.org/mailman/listinfo/mico-devel


Re: [mico-devel] Building mico on Cygwin

2006-10-12 Thread Karel Gardas


Hi,

I'm curious if the change in LDLIBS is unnecessary or not. Could you be so 
kind and:


1) check that you do have -lssl -lcrypto defined in CONFLIBS variable in 
top-level MakeVars file


and

2) apply attached patch and test if it is working correctly? (you'll 
needed to revert your changes first)


I don't have cygwin platform here so I'm not able to test it myself.

Thanks,
Karel
--
Karel Gardas  [EMAIL PROTECTED]
ObjectSecurity Ltd.   http://www.objectsecurity.com
---
Need experienced, fast, reliable technical MICO support?
--- http://www.objectsecurity.com/mico_commsup_referral.html ---
---

On Wed, 11 Oct 2006, Arun Biyani wrote:


Patrick Gräbel wrote:

Hi!

I experienced the same linking problem, but I solved it by adding the
lib crypto (and maybe ssl) somewhere in the Makefile. Search for
gcc's -l parameter inside the Makefile (maybe more than a single one).

Seems that libssl depends on libcrypto which does not get linked via the
make procedure.

After building MICO you always have to link libcrypto/libssl to your
MICO-based projects.

-Patrick
___
Mico-devel mailing list
Mico-devel@mico.org
http://www.mico.org/mailman/listinfo/mico-devel





Thx Patrick for the hint. It was file mico/ir/Makefile. I had to

LDLIBS   := -lssl -lcrypto -lidl $(LDMICOIR) $(LDMICO) $(CONFLIBS)

PLATFORM_LIBS = -lssl -lcrypto

It works fine now.
Thx
Arun


___
Mico-devel mailing list
Mico-devel@mico.org
http://www.mico.org/mailman/listinfo/mico-devel--- old-mico/ir/Makefile2006-02-18 21:49:57.0 +0100
+++ new-mico/ir/Makefile2006-10-12 10:07:43.0 +0200
@@ -28,7 +28,7 @@
 
 PLATFORM_LIBS =
 ifeq ($(HAVE_CYGWIN), yes)
-PLATFORM_LIBS := $(PLATFORM_LIBS) ../orb/libmico$(VERSION).$(SOEXT)
+PLATFORM_LIBS := $(PLATFORM_LIBS) $(CONFLIBS) ../orb/libmico$(VERSION).$(SOEXT)
 endif
 
 ifeq ($(HAVE_EXCEPTIONS), yes)

___
Mico-devel mailing list
Mico-devel@mico.org
http://www.mico.org/mailman/listinfo/mico-devel


Re: [mico-devel] Building mico on Cygwin

2006-10-12 Thread Arun Biyani

Karel Gardas wrote:


Hi,

I'm curious if the change in LDLIBS is unnecessary or not. Could you 
be so kind and:


1) check that you do have -lssl -lcrypto defined in CONFLIBS variable 
in top-level MakeVars file


and

2) apply attached patch and test if it is working correctly? (you'll 
needed to revert your changes first)


I don't have cygwin platform here so I'm not able to test it myself.

Thanks,
Karel
--
Karel Gardas  [EMAIL PROTECTED]
ObjectSecurity Ltd.   http://www.objectsecurity.com
---
Need experienced, fast, reliable technical MICO support?
--- http://www.objectsecurity.com/mico_commsup_referral.html ---
---

On Wed, 11 Oct 2006, Arun Biyani wrote:


Patrick Gräbel wrote:

Hi!

I experienced the same linking problem, but I solved it by adding the
lib crypto (and maybe ssl) somewhere in the Makefile. Search for
gcc's -l parameter inside the Makefile (maybe more than a single 
one).


Seems that libssl depends on libcrypto which does not get linked via 
the

make procedure.

After building MICO you always have to link libcrypto/libssl to your
MICO-based projects.

-Patrick
___
Mico-devel mailing list
Mico-devel@mico.org
http://www.mico.org/mailman/listinfo/mico-devel





Thx Patrick for the hint. It was file mico/ir/Makefile. I had to

LDLIBS   := -lssl -lcrypto -lidl $(LDMICOIR) $(LDMICO) $(CONFLIBS)

PLATFORM_LIBS = -lssl -lcrypto

It works fine now.
Thx
Arun


___
Mico-devel mailing list
Mico-devel@mico.org
http://www.mico.org/mailman/listinfo/mico-devel
I started in a new directory. After configure, I checked the MakeVars. 
It did have
-lssl  -lcrypto. Then I applied the patch. It worked perfectly. No 
errors when I

did a make.

Arun

mico$:722] cd ir
/c/tmp/spg/mico/ir
/c/tmp/spg/mico/ir
[ir$:723] ls
Makefile   Makefile.win32  ir3.cc   ir_all.cc   ir_impl.h  
ir_skel.cc

Makefile.diff  ir.cc.diffs ir3_skel.cc  ir_impl.cc  ir_pch.h   main.cc
[ir$:724] patch  Makefile.diff
(Stripping trailing CRs from patch.)
patching file Makefile
[ir$:725]


___
Mico-devel mailing list
Mico-devel@mico.org
http://www.mico.org/mailman/listinfo/mico-devel


Re: [mico-devel] Building mico on Cygwin

2006-10-10 Thread Patrick Gräbel
Hi!

I experienced the same linking problem, but I solved it by adding the
lib crypto (and maybe ssl) somewhere in the Makefile. Search for
gcc's -l parameter inside the Makefile (maybe more than a single one).

Seems that libssl depends on libcrypto which does not get linked via the
make procedure.

After building MICO you always have to link libcrypto/libssl to your
MICO-based projects.

-Patrick
___
Mico-devel mailing list
Mico-devel@mico.org
http://www.mico.org/mailman/listinfo/mico-devel