So if no one with more experience than me objects, I propose you fix import-backend.c in a separate commit as well. I think they can be avoided in this case.
GNUCASH IMPORT CSV FILE FORMAT CODE
I realize you took the import-backend.c code as example, which also uses the extern definitions. Or perhaps even to Account.h and consider these as public interface to the Account object. I'd prefer to move the prototypes to AccountP.h and include that header file instead. Because the prototypes are in the source file and not in some (private) header file you are forced to use extern declarations to use these functions. Having said that however, I'm not too fond of this construct. For the other gnc_imap_* functions these prototypes are defined around line 5040 in the same file. You probably forgot to add a function prototype for gnc_imap_delete_account. Makefile:942: recipe for target 'libgncmod_engine_la-Account.lo' failed Gnc_imap_delete_account (GncImportMatchMap *imap,Ĭc1: all warnings being treated as errors kobaltnet/janssege/Development/gnucash/gnucash-master/src/engine/Account.c:5116:1: error: no previous prototype for 'gnc_imap_delete_account' deps/libgncmod_engine_la-Account.Tpo -c /kobaltnet/janssege/Development/gnucash/gnucash-master/src/engine/Account.c -fPIC -DPIC -o. I/kobaltnet/janssege/Development/gnucash/gnucash-master/lib/libc -I/kobaltnet/janssege/Development/gnucash/gnucash-master/src/core-utils -I/kobaltnet/janssege/Development/gnucash/gnucash-master/src -I././src -I/kobaltnet/janssege/Development/gnucash/gnucash-master/src/gnc-module -I/kobaltnet/janssege/Development/gnucash/gnucash-master/src/libqof/qof -pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -pthread -I/usr/include/guile/2.0 -I/usr/include -DG_LOG_DOMAIN=\"gnc.engine\" -Werror -Wdeclaration-after-statement -Wno-pointer-sign -Wall -Wunused -Wmissing-prototypes -Wmissing-declarations -Wno-unused -g -std=gnu99 -g -MT libgncmod_engine_la-Account.lo -MD -MP -MF. I/kobaltnet/janssege/Development/gnucash/gnucash-master/src/engine -I./. Libtool: compile: gcc -DHAVE_CONFIG_H -I. deps/libgncmod_engine_la-Account.Tpo -c -o libgncmod_engine_la-Account.lo `test -f 'Account.c' || echo '/kobaltnet/janssege/Development/gnucash/gnucash-master/src/engine/'`Account.c
/libtool -tag=CC -mode=compile gcc -DHAVE_CONFIG_H -I. Make: Entering directory '/kobaltnet/janssege/Development/builds/gnucash/master/src/engine' Early over-generalization is a bug, just like premature optimization. I don't think that an OFX or QIF import is likely to contain GnuCash accounts since GnuCash has no facility for exporting either format. So lose the file and save the association data to the book's KVP, ideally using the same mechanism as the non-Bayesian matcher for OFX. Try running `gnucash -nofile`: You'll see that the title bar says "Unsaved Book". You might start with an empty book, but GnuCash won't do anything without a book. There is no "start with no current file". > The reason for the location and extra types was that maybe it could be used > valid file name as this should only happen once. > map file name on, maybe I will only save the account mappings when we have a In this case there is no Gnucash file name to base the > current file and use a CSV file for input with you creating matching > reason I chose this one is that there is a use case when you start with no > I was in two minds about the directory / file name when I did this. Test the match text for valid account path Allow the Account Matcher dialog to close automatically.
0 kommentar(er)
