Dear Developers,

i have been silent for the last few month. I simply couln't affort the time to 
get needed progress to my branches.

Since Eastern holidays gave me some spare time, here is some status update:

CoOwner 4  
=========  
First  i had a look and rebased on latest v4 branch.  
This did work out as expected. Code is availabe on following link: 
https://github.com/rzerres/gnucash/tree/coowner-4  
 It compiles and offers the given functionality.
  
CoOwner 5  
=========  
As a next step i started to port the code to lastest stable (ala v5:  
[https://github.com/rzerres/gnucash/tree/wip-coowner-5](https://github.com/rzerres/gnucash/tree/wip-coowner-5)).

Oviously the braking changes required to update UI and module handling.  
Beside some cleanup, i succeeded for the backend (xml, sql, dbi), register and 
engine code. No compiler errors or warnings.

Inside gnucash/gnome there has been progress on the wip-code.  
I'm aiming to implement CoOwner settlements, which does require a quite 
substantial changes in the dialog, gtkbuilder and involved plugin code (e.g: 
billterms, job, invoice, distriblist).

dialog-distriblists isn't finished. Compiler warnings (mainly unused-variables) 
are expected right now. 

Help needed  
===========

When compiling, i do get stuck to understand, why the linker breaks when 
linking `gnucash` binary.
It can't resolve lables inside `libgnc-backend-xml-utils.so`.

```  
Linking CXX executable ../bin/gnucash  
/usr/bin/ld: ../lib/libgnc-backend-xml-utils.so: undefined reference to 
`gncCoOwnerSetTerms(_gncCoOwner*, _gncBillTerm*)'
...
/usr/bin/ld: ../lib/libgnc-backend-xml-utils.so: undefined reference to 
`gncCoOwnerGetAptShare(_gncCoOwner const*)'
collect2: error: ld returned 1 exit status
 
```  

I would appreciate, if someone with better knowledge could give me a light. 
Thanks in advance.

Regards,
Ralf Zerres







_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Reply via email to