やっと知る事ができたのでメモ
1 #include <stdio.h>
2
3 int main(void){
4
5 printf("error message in %s line: %d\n",__FILE__,__LINE__);
6
7 return 0;
8 }
標準出力
error message in test.c line: 5
reate database wikidb; grant create, select, insert, update, delete, alter, lock tables, index on wikidb.* to 'wikiuser'@'localhost' identified by 'password'; flush privileges;
create database redmine character set utf8; create user 'redmine'@'localhost' identified by 'my_password'; grant all privileges on redmine.* to 'redmine'@'localhost';
rake generate_session_store
RAILS_ENV=production rake db:migrate
RAILS_ENV=production rake redmine:load_default_data
ruby script/server webrick -e production
set logscale cbpm3dでカラーバーに表示される数字のフォーマットを変更
set format cb "10^{%L}"ylabelの位置を変える
set ylabel "hogehoge" -1,0
#ifndef HELLO_H #define HELLO_H void sayHello(); #endif
#include#include"hello.h" void sayHello(){ printf("Hello!!\n"); }
gcc -I ${HOME}/include/ -fPIC -shared hello.c -o ${HOME}/lib/libhello.so.1そして、${HOME}/lib/にて、シンボリックリンクを作成。新しいバージョンができたらこのリンクを作り替える。
ln -s libhello.so.1 libhello.soさらにライブラリを使う側を実装。
#include"hello.h" int main(){ sayHello(); return 0; }そして、コンパイル。
gcc -I ${HOME}/include -L${HOME}/lib -lhello use.c-lで、「libhello.so」のlibと拡張子を除いたものを指定。-LでそのライブラリのPATHを指定する。
./a.outなどど実行すると。
./a.out: error while loading shared libraries: libhello.so: cannot open shared object file: No such file or directoryと叱られる。ライブラリの検索PATHに${HOME}/libが無いためである。ここで普通は、LD_LIBRARY_PATHに${HOME}/libを追加するのだが、Ubuntuでは、ldconfigを使うらしい。
/home/hoge/libそして、設定を反映させるために
sudo ldconfigすると無事ライブラリを使用したプログラムを実行できる
./a.outまた、リンクするライブラリを確認するには、
ldd a.out
#include以下がi386環境での実行結果#include int main(int argc,char **argv){ printf("size of char: %d bit\n",CHAR_BIT); printf(" char range is %d -> %d\n",CHAR_MIN,CHAR_MAX); printf(" signed char range is %d -> %d\n",SCHAR_MIN,SCHAR_MAX); printf("unsigned char range is 0 -> %u\n",UCHAR_MAX); printf(" int range is %d -> %d\n",INT_MIN,INT_MAX); printf("unsigned int range is 0 -> %u\n",UINT_MAX); printf(" short range is %d -> %d\n",SHRT_MIN,SHRT_MAX); printf("unsigned short range is 0 -> %u\n",USHRT_MAX); printf(" long range is %ld -> %ld\n",LONG_MIN,LONG_MAX); printf("unsigned long range is 0 -> %lu\n",ULONG_MAX); return 0; }
size of char: 8 bit char range is -128 -> 127 signed char range is -128 -> 127 unsigned char range is 0 -> 255 int range is -2147483648 -> 2147483647 unsigned int range is 0 -> 4294967295 short range is -32768 -> 32767 unsigned short range is 0 -> 65535 long range is -2147483648 -> 2147483647 unsigned long range is 0 -> 4294967295以下がamd64環境での実行結果
size of char: 8 bit char range is -128 -> 127 signed char range is -128 -> 127 unsigned char range is 0 -> 255 int range is -2147483648 -> 2147483647 unsigned int range is 0 -> 4294967295 short range is -32768 -> 32767 unsigned short range is 0 -> 65535 long range is -9223372036854775808 -> 9223372036854775807 unsigned long range is 0 -> 18446744073709551615
sudo apt-get install doxygenでOK
doxygen -g hoge.confこれで、標準的な出力設定ファイルが生成される。名前は、任意でOK.
doxygen hoge.confとすると./html/index.htmlが出力されます。
*** org.conf 2012-07-28 13:39:06.803258079 +0900 --- common.conf 2012-07-28 13:36:44.702147423 +0900 *************** *** 25,31 **** # The PROJECT_NAME tag is a single word (or a sequence of words surrounded # by quotes) that should identify the project. ! PROJECT_NAME = # The PROJECT_NUMBER tag can be used to enter a project or revision number. # This could be handy for archiving the generated documentation or --- 25,31 ---- # The PROJECT_NAME tag is a single word (or a sequence of words surrounded # by quotes) that should identify the project. ! PROJECT_NAME = "First use of doxygen" # The PROJECT_NUMBER tag can be used to enter a project or revision number. # This could be handy for archiving the generated documentation or *************** *** 199,205 **** # sources only. Doxygen will then generate output that is more tailored for # Fortran. ! OPTIMIZE_FOR_FORTRAN = NO # Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL # sources. Doxygen will then generate output that is tailored for --- 199,205 ---- # sources only. Doxygen will then generate output that is more tailored for # Fortran. ! OPTIMIZE_FOR_FORTRAN = YES # Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL # sources. Doxygen will then generate output that is tailored for *************** *** 297,313 **** # Private class members and static file members will be hidden unless # the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES ! EXTRACT_ALL = NO # If the EXTRACT_PRIVATE tag is set to YES all private members of a class # will be included in the documentation. ! EXTRACT_PRIVATE = NO # If the EXTRACT_STATIC tag is set to YES all static members of a file # will be included in the documentation. ! EXTRACT_STATIC = NO # If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) # defined locally in source files will be included in the documentation. --- 297,313 ---- # Private class members and static file members will be hidden unless # the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES ! EXTRACT_ALL = YES # If the EXTRACT_PRIVATE tag is set to YES all private members of a class # will be included in the documentation. ! EXTRACT_PRIVATE = YES # If the EXTRACT_STATIC tag is set to YES all static members of a file # will be included in the documentation. ! EXTRACT_STATIC = YES # If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) # defined locally in source files will be included in the documentation. *************** *** 591,597 **** # *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx # *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py *.f90 ! FILE_PATTERNS = # The RECURSIVE tag can be used to turn specify whether or not subdirectories # should be searched for input files as well. Possible values are YES and NO. --- 591,597 ---- # *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx # *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py *.f90 ! FILE_PATTERNS = *.f # The RECURSIVE tag can be used to turn specify whether or not subdirectories # should be searched for input files as well. Possible values are YES and NO. *************** *** 690,701 **** # Note: To get rid of all source code in the generated output, make sure also # VERBATIM_HEADERS is set to NO. ! SOURCE_BROWSER = NO # Setting the INLINE_SOURCES tag to YES will include the body # of functions and classes directly in the documentation. ! INLINE_SOURCES = NO # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct # doxygen to hide any special comment blocks from generated source code --- 690,701 ---- # Note: To get rid of all source code in the generated output, make sure also # VERBATIM_HEADERS is set to NO. ! SOURCE_BROWSER = YES # Setting the INLINE_SOURCES tag to YES will include the body # of functions and classes directly in the documentation. ! INLINE_SOURCES = YES # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct # doxygen to hide any special comment blocks from generated source code *************** *** 1389,1395 **** # toolkit from AT&T and Lucent Bell Labs. The other options in this section # have no effect if this option is set to NO (the default) ! HAVE_DOT = NO # By default doxygen will write a font called FreeSans.ttf to the output # directory and reference it in all dot files that doxygen generates. This --- 1389,1395 ---- # toolkit from AT&T and Lucent Bell Labs. The other options in this section # have no effect if this option is set to NO (the default) ! HAVE_DOT = YES # By default doxygen will write a font called FreeSans.ttf to the output # directory and reference it in all dot files that doxygen generates. This *************** *** 1464,1470 **** # the time of a run. So in most cases it will be better to enable call graphs # for selected functions only using the \callgraph command. ! CALL_GRAPH = NO # If the CALLER_GRAPH and HAVE_DOT tags are set to YES then # doxygen will generate a caller dependency graph for every global function --- 1464,1470 ---- # the time of a run. So in most cases it will be better to enable call graphs # for selected functions only using the \callgraph command. ! CALL_GRAPH = YES # If the CALLER_GRAPH and HAVE_DOT tags are set to YES then # doxygen will generate a caller dependency graph for every global function *************** *** 1472,1478 **** # the time of a run. So in most cases it will be better to enable caller # graphs for selected functions only using the \callergraph command. ! CALLER_GRAPH = NO # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen # will graphical hierarchy of all classes instead of a textual one. --- 1472,1478 ---- # the time of a run. So in most cases it will be better to enable caller # graphs for selected functions only using the \callergraph command. ! CALLER_GRAPH = YES # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen # will graphical hierarchy of all classes instead of a textual one.ソースコメント記入例
!----------------------------------------------------------- ! MODULE: test program !> @author !> Author name ! ! DESCRIPTION: !> test program for using doxigen ! REVISION HISTORY: ! 16 Apr 2012 - Initial Version ! TODO_28_jul_2012 - add explain of subroutine add - todo1 !----------------------------------------------------------- program test integer a,b a=1 b=2 write(*,*) a call add(a) write(*,*) a call add(b) end !> Subroutine add !> @param[in] sa you want to add 1 !> @brief ! add 1 to argument subroutine add(sa) integer sa sa = sa + 1 end
複数の要素が有機的に関係しあい、全体としてまとまった機能を発揮している要素の集合体とある。さらに私的には、最後の「の集合体」を削除した意味としたい。つまり、複数の要素の集合も要素という風に解釈するのである(再帰的な表現)。
複雑系は、階層を持たない平坦なページを使い、タグでグループ分けするのが基本だ。ここでは、哲学的に昇華させるとすれば下記だと思う。
int main(int argc,char **argv){ printf("Hello Worild!!\n"); return 0; }
gnuplot> set dgrid3d 30,30 gnuplot> set hidden3d
#include<stdio.h>
#include<stdlib.h>
#include<gsl/gsl_sf_bessel.h>
int main(int argc,char** argv){
int min,max,num,i,j;
double x,xmin,xmax,xdel;
double *result;
max=100;
min=1;
num=max-min+1;
xmin=0;
xmax=50;
xdel=0.5;
result=malloc(sizeof(double)*num);
for(x=xmin;x<=xmax;x+=xdel){
gsl_sf_bessel_Jn_array(min,max,x,result);
printf("%f ",x);
for(j=0;j<=num-1;j++){
printf("%f ",result[j]);
}
printf("\n");
}
free(result);
return 0;
}
MASTER_SITE_OVERRIDE?=ftp://ftp.jp.FreeBSD.org/pub/FreeBSD/ports/distfiles/${DIST_SUBDIR}/
Before | After | |
LayerDriver JPN | kbd106.dll | kbd103.dll |
OverrideKeyboardIdentifier | PCAT_106KEY | PCAT_103KEY |
OverrideKeyboardSubtype | 2 | 0 |
愛機xperiaの動作が最近不安定で再起動連発なので今日ショップにいってみた
はっきり言って専門のスタッフじゃないと分かりかねますのでケータイをお預かりします的な流れを予想していたが
ドコモの店員さんも結構やるじゃんという対応だった
まず始めにインストールしているアプリをチェックされた
そして、その次に電池パックの付け直し
最後に専用の機械で電池の充電量を確かめてみた
するとOS的には(ステータスバーでは)ほぼフル充電表示にもかかわらずその機械で測ると17%しか充電されていなかった
この端末は発売日(2009/04/01)に買ったのでそろそろ二年たつ
動作の不安定性と関係があるかは分からないが電池は取り替え時らしい
OSの情報と実態との乖離があるというのは自分では以外だったし
何よりも失礼だがドコモの店員さんでここまで対応してもらえると思ってなかったので驚いた
\pagestyle{headings}としてしまっていて章見出しがヘッダーに出力されている.
\pagestyle{headnombre}とすればいい.
pstoedit -f tgif input.eps output.objでobj形式のファイルを生成する. (ちなみに, pstoeditは入ってなかったのでソフトウェアセンターからインストール)そして, 以下のコマンドでobjファイルをtgifで開く.
tgif output.obj &修正が完了したら保存してtgifを閉じる. そして, objファイルをepsに変換する.
tgif -print -eps -color output.objそうするとoutput.epsが出力される.
/usr/bin/gnome-settings-deamon &