From: Stefan J. <st...@gr...> - 2006-03-28 08:41:19
|
Am Mo, 27.03.2006, 21:41, schrieb thierry scordilis: > hello, Hi! > The re-install is now working, I will recompile the version 0.0.9 > tomorrow, but I'm facing some trouble with freeHDL. Good luck. > I will try to rewrite some things on the workbook, in order to finish > the opened chapters, Sounds good... > by the way is there a tutorial for creating a new > component in qucs ( it could be useful in order to test new models ) I > have in mind to produce some system blocks ... in order to write some > specs Erm. You mean subcircuits? >... and why not create some files for octave to produce some > system simulation )... Hm. What do you mean? Regards, Stefan. |
From: Stefan J. <st...@gr...> - 2006-03-28 10:28:12
|
Am Di, 28.03.2006, 12:12, schrieb thierry scordilis: Hello! > I do not mean sub-circuit but new components like the hybrid coupler, > amplifier, isolator ,... I want to add some filtering functions > including the noise figure ... > > The idea is to work a little on base band issue ... > > Am I correct if I look for amplifier.cpp/.h in qucs and amplifier.cpp > in qucs-core in there any other files to modify (as an example) it > could be good to document this ... This is about API documentation, correct? I don not know if this is a good idea at this stage of development. I hope these interfaces do not change too much in future, but it may happen. So in fact it would be good to do that. On the other hand it is probably better to wait for a development stage when the API is available as a standalone library interface with user-defined models possible... I remember you made this suggestion already and it is on the TODO list, but currently there are also other issues I am working at... Also this is than a major change in the interface and everything would have to be rewritten somehow. I would really appreciate if you first review the other tutorials or even add some new about *using* Qucs for circuit design issues. This is a field where only very few things exist and users (and novices as well) of Qucs would appreciate this as well. Thanks in advance, Stefan. |
From: Stefan J. <st...@gr...> - 2006-03-28 13:42:41
|
Am Di, 28.03.2006, 13:59, schrieb thierry scordilis: hi there! > it copiles a little furhter but the problem is in the stdlib it seems : > > main.cc: In function `int kernel_main(int, char**, handle_info*)': > main.cc:1192: error: invalid use of undefined type `struct socket' can you tell where "struct socket" is defined in your header files? > I will try to use Cver from www.pragmatic-c.com/gpl-cver/ in order to run digital simulations with qucs you *have* to install freehdl. the verilog hdl simulator Cver is not an option... cheers, stefan. |
From: Stefan J. <st...@gr...> - 2006-04-03 13:05:28
|
Am Mo, 3.04.2006, 13:22, schrieb thierry scordilis: Hello! > $ flex --version > flex version 2.5.4 > $ bison --version > GNU Bison version 1.28 Please see the RELEASE file for which versions of bison/flex are required. The version you've are apparently tooo old. > with --enable-maitainer-mode option : > > the returned message is > > bison -y -v -o parse_dataset.cpp --defines=tokens_dataset.h > parse_dataset.y > bison: option `--defines' doesn't allow an argument > Usage: bison [-dhklntvyV] [-b file-prefix] [-o outfile] [-p name-prefix] > [--debug] [--defines] [--fixed-output-files] [--no-lines] > [--verbose] [--version] [--help] [--yacc] > [--no-parser] [--token-table] > [--file-prefix=prefix] [--name-prefix=prefix] > [--output=outfile] grammar-file > > > > > On Apr 3, 2006, at 12:56 PM, Stefan Jahn wrote: > >> Am Mo, 3.04.2006, 10:44, schrieb thierry scordilis: >> >> Hello Thierry! >> >>> hi I still have a problem on 009 when compiling ... >>> >>> if g++ -DHAVE_CONFIG_H -I. -I. -I.. -I../src/components -O2 -pipe >>> -fno-exceptions -fno-rtti -fno-check-new -MT dataset.o -MD -MP -MF >>> ".deps/dataset.Tpo" -c -o dataset.o dataset.cpp; \ >>> then mv -f ".deps/dataset.Tpo" ".deps/dataset.Po"; else rm -f >>> ".deps/dataset.Tpo"; exit 1; fi >>> if g++ -DHAVE_CONFIG_H -I. -I. -I.. -I../src/components -O2 -pipe >>> -fno-exceptions -fno-rtti -fno-check-new -MT check_dataset.o -MD -MP >>> -MF ".deps/check_dataset.Tpo" -c -o check_dataset.o check_dataset.cpp; >>> \ >>> then mv -f ".deps/check_dataset.Tpo" ".deps/check_dataset.Po"; else rm >>> -f ".deps/check_dataset.Tpo"; exit 1; fi >>> make[3]: *** No rule to make target `parse_dataset.cpp', needed by >>> `parse_dataset.o'. Stop. >>> make[2]: *** [all-recursive] Error 1 >>> make[1]: *** [all-recursive] Error 1 >>> make: *** [all] Error 2 >> >> With CVS sources you need both flex and bison installed... Also you >> need to >> >> ./configure --enable-maintainer-mode ... >> >> Then the "rule to make target `parse_dataset.cpp'" will be created in >> the Makefile's. Stefan. |
From: Stefan J. <st...@gr...> - 2006-04-03 14:26:55
|
Am Mo, 3.04.2006, 15:45, schrieb SCORDILIS Thierry: Hi there! > the latest for osX 10.3 are : > > flex 2.5.4a2 or flex-devel 2.5.31 > bison 1.35-2 These are the requirements for Qucs: + flex 2.5.31 + GNU M4 (any version) + GNU Bison 1.875d So you may try with 'flex-devel 2.5.31' and a self-build of a newer bison version. Download from <http://ftp.gnu.org/gnu/bison/>. Stefan. >>>$ flex --version >>>flex version 2.5.4 >>>$ bison --version >>>GNU Bison version 1.28 >> >> >> Please see the RELEASE file for which versions of bison/flex are >> required. >> The version you've are apparently tooo old. >> >> >>>with --enable-maitainer-mode option : >>> >>>the returned message is >>> >>>bison -y -v -o parse_dataset.cpp --defines=tokens_dataset.h >>>parse_dataset.y >>>bison: option `--defines' doesn't allow an argument >>>Usage: bison [-dhklntvyV] [-b file-prefix] [-o outfile] [-p name-prefix] >>> [--debug] [--defines] [--fixed-output-files] [--no-lines] >>> [--verbose] [--version] [--help] [--yacc] >>> [--no-parser] [--token-table] >>> [--file-prefix=prefix] [--name-prefix=prefix] >>> [--output=outfile] grammar-file >>> >>> >>> >>> >>>On Apr 3, 2006, at 12:56 PM, Stefan Jahn wrote: >>> >>> >>>>Am Mo, 3.04.2006, 10:44, schrieb thierry scordilis: >>>> >>>>Hello Thierry! >>>> >>>> >>>>>hi I still have a problem on 009 when compiling ... >>>>> >>>>>if g++ -DHAVE_CONFIG_H -I. -I. -I.. -I../src/components -O2 -pipe >>>>>-fno-exceptions -fno-rtti -fno-check-new -MT dataset.o -MD -MP -MF >>>>>".deps/dataset.Tpo" -c -o dataset.o dataset.cpp; \ >>>>>then mv -f ".deps/dataset.Tpo" ".deps/dataset.Po"; else rm -f >>>>>".deps/dataset.Tpo"; exit 1; fi >>>>>if g++ -DHAVE_CONFIG_H -I. -I. -I.. -I../src/components -O2 -pipe >>>>>-fno-exceptions -fno-rtti -fno-check-new -MT check_dataset.o -MD -MP >>>>>-MF ".deps/check_dataset.Tpo" -c -o check_dataset.o check_dataset.cpp; >>>>>\ >>>>>then mv -f ".deps/check_dataset.Tpo" ".deps/check_dataset.Po"; else rm >>>>>-f ".deps/check_dataset.Tpo"; exit 1; fi >>>>>make[3]: *** No rule to make target `parse_dataset.cpp', needed by >>>>>`parse_dataset.o'. Stop. >>>>>make[2]: *** [all-recursive] Error 1 >>>>>make[1]: *** [all-recursive] Error 1 >>>>>make: *** [all] Error 2 >>>> >>>>With CVS sources you need both flex and bison installed... Also you >>>>need to >>>> >>>> ./configure --enable-maintainer-mode ... >>>> >>>>Then the "rule to make target `parse_dataset.cpp'" will be created in >>>>the Makefile's. |