All right. Most of my experience comes from the Java side, so I may need some handholding as I get into this C++ world. Also, my only Open Source work was a small contribution to HttpUnit, so if you could point me to a FAQ for open source or provide some tips for how you're managing this project (i.e. should I send changes to you, or commit them to CVS directly?), I would appreciate it.
As an immediate observation, when I ran configure, snprintf was reported as not existing, while it does actually exist. In order to get configure to acknowledge a legit snprintf, I changes aclocal.m4 as follows:
389 jkimball@bonnie> diff aclocal.m4 aclocal.m4~
3539c3539
< int main () { char buffer[80]; exit (!(3 <= snprintf(buffer,80,"%d",100))); }
---
> int main () { exit (!(3 <= snprintf(NULL,0,"%d",100))); }
I am using g++ ver 2.95.3 and Solaris 7.
I haven't gotten too far into using the code yet, so I don't know if I've broken things or not.
I am going to try to use log4cpp in my app so I will help out where I can.
Jim
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There is no FAQ (yet), but I do have some tips:
Join the development mailing list and discuss any development issues there. If you have small patches you can mail them to. For larger ones use the patch manager on the project page.
If you regularly contribute, most likely I'll invite you to become a project member. This will give you direct CVS write access.
In general: please adhere to the coding style used in the project (which mostly is the Java coding standard), create patches agains CVS HEAD, and put separate fixes/enhancements in separate diffs.
Regarding the snprintf detection: the M4 macro tests for a C99 standard compliant snprintf, not just existance. Apparently Solaris 7 is not compliant. Ah, well.
Thanks,
Bastiaan
PS. the coming days I'll be at HAL2001, and won't read my mail. Sorry...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Is this project still active? I was going to try to get this app running under g++ on Solaris.
Hello?
Jim
It's still alive Jim, it's still alive.
If you feel development is going too slow, you're welcome to contribute....
Bastiaan
All right. Most of my experience comes from the Java side, so I may need some handholding as I get into this C++ world. Also, my only Open Source work was a small contribution to HttpUnit, so if you could point me to a FAQ for open source or provide some tips for how you're managing this project (i.e. should I send changes to you, or commit them to CVS directly?), I would appreciate it.
As an immediate observation, when I ran configure, snprintf was reported as not existing, while it does actually exist. In order to get configure to acknowledge a legit snprintf, I changes aclocal.m4 as follows:
389 jkimball@bonnie> diff aclocal.m4 aclocal.m4~
3539c3539
< int main () { char buffer[80]; exit (!(3 <= snprintf(buffer,80,"%d",100))); }
---
> int main () { exit (!(3 <= snprintf(NULL,0,"%d",100))); }
I am using g++ ver 2.95.3 and Solaris 7.
I haven't gotten too far into using the code yet, so I don't know if I've broken things or not.
I am going to try to use log4cpp in my app so I will help out where I can.
Jim
There is no FAQ (yet), but I do have some tips:
Join the development mailing list and discuss any development issues there. If you have small patches you can mail them to. For larger ones use the patch manager on the project page.
If you regularly contribute, most likely I'll invite you to become a project member. This will give you direct CVS write access.
In general: please adhere to the coding style used in the project (which mostly is the Java coding standard), create patches agains CVS HEAD, and put separate fixes/enhancements in separate diffs.
Regarding the snprintf detection: the M4 macro tests for a C99 standard compliant snprintf, not just existance. Apparently Solaris 7 is not compliant. Ah, well.
Thanks,
Bastiaan
PS. the coming days I'll be at HAL2001, and won't read my mail. Sorry...