I'm creating a wifi application using ESP-IDF based on the examples but the example I'm using has options for setting the SSID and PASSWORD under:
Example Connection Configuration
when using idf.py menuconfig and which are used by CONFIG_EXAMPLE_WIFI_SSID and CONFIG_EXAMPLE_WIFI_PASSWORD in the code.
I want to set SSID and PASSWORD in my own project without using this in CMakeLists.txt:
set(EXTRA_COMPONENT_DIRS $ENV{IDF_PATH}/examples/common_components/protocol_examples_common)
without the above there isn't a way to define SSID and PASSWORD. They appear in:
build/config/kconfig_menus.json
but I can't seem to keep this from being overwritten in my own project. sdkconfig states it should not be edited.
Is there a best practice for using idf.py menuconfig? Or do most people just use sdkconfig.defaults and not use idf.py menuconfig?
I eventually tracked down the file Kconfig.projbuild in the example project via the build system docs:
Each component may also include a Kconfig file defining the component
configuration options that can be set via menuconfig. Some components
may also include Kconfig.projbuild and project_include.cmake files,
which are special files for overriding parts of the project.
created my own version and put it in main and the options now appear when using idf.py menuconfig. Thanks to this video.
When we use ESP-IDF example and change config using idf.py menuconfig there is one config option example configuration that is custom or user's own configuration created by espressif. And we can also make our own configuration like that.
Kconfig.projbuild is used for making our own configuration. for details see below links.
how-to-add-custom-configuration-in-project-config
Espressif official doc
Related
I'm following instructions here and it says that I will find a bitcoin.conf file Windows: %APPDATA%\Bitcoin\ and
To use bitcoind and bitcoin-cli, you will need to add a RPC password to your bitcoin.conf file. Both programs will read from the same file if both run on the same system as the same user, so any long random password will work: rpcpassword=change_this_to_a_long_random_password
However When I navigate to %APPDATA%\Bitcoin\ I don't see a bitcoin.conf file.
So What do I do? Do I add a bitcoin.conf file? There is a bitcoin-conf.md file in doc in my bitcoin install directory so maybe somthing todo with that? I really don't know. Thanks for pointing me in the right direction.
That guide does not take into account the fact that you do not have to add any RPC user or password to your configuration file for the past some years.
Bitcoind will generate a cookie that allows the CLI (command line interface) to communicate with the Bitcoin daemon using RPC without the user having had to give it a single thought.
That is a developers' guide, so developers may have more complex requirements that are solved if they specify their own RPC authentication settings, such as running multiple wallets, or possibly exchange software that communicates with the wallet or multiple wallets.
bitcoin.conf being optional, it is not by default created, and is not needed for ordinary usage, only becoming necessary when the user or developer has particular, non-default settings to set.
The possible settings can be found by the help command bitcoind -help and lists a number of command line parameters (beginning with a dash or hyphen) that can be typed or pasted after bitcoind on the command line, but can be put in a text file named bitcoin.conf without the minus sign before the command. For example: -connect=IPAddress becomes simply connect=IPAddress in the conf file.
For creating suitable rpcauth (username and hashed password), and rpcuser and rpcpassword values, I've found some resources such as https://github.com/jlopp/bitcoin-core-rpc-auth-generator
Rather than serving JLopp's RPC auth generator locally you can simply copy from, or use a Python script found in the Bitcoin repository under the folder named "share", you will see a folder called rpcauth which contains the rpcauth.py script and a small explanatory file called README.md.
You have to create this file and put a single line rpcpassword=<your_password> in it.
bitcoin-conf.md contains documentation for this btcoin.conf and particularily states:
The configuration file is not automatically created; you can create it using your favorite text editor.
Recommended reading this doc. It may help you to facilitate running your node.
I want to place files a.idl, b.idl in the folder at the link https://github.com/RedhawkSDR/framework-core/tree/master/src/idl/ossie/CF
And I also include a.idl and b.idl in the makefile at this link
https://github.com/RedhawkSDR/framework-core/tree/master/src/idl
As is done for all other idl file mentioned above.
But these are not compiled as I am not able to see them anywhere.
Please provide any inputs
In addition to including, a.idl and b.idl in the file "Makefile.am" at this link https://github.com/RedhawkSDR/framework-core/tree/master/src/idl , we have to do the following in the "Makefile.am" present at the link https://github.com/RedhawkSDR/framework-core/tree/master/src/base/framework/idl
Add aSK.cpp, aDynSK.cpp, bSK.cpp, bDynSK.cpp to the "BUILT_SOURCES" variable defined in the file.
With this done, now we can see the skeleton and stub codes in the folders at following links :
https://github.com/RedhawkSDR/framework-core/tree/master/src/base/framework/idl
and
this folder which will be generated on running the install command "RedhawkSDR/framework-core/tree/master/src/base/include/ossie/CF/"
REDHAWK's IDL is split into two main categories: core services and ports. Core services are related to REDHAWK's core functionality, like deploying an application. Ports are application-specific interfaces for communicating between different processing stages (components or devices). Core services are not meant to be extended, while ports are meant to be extended by the user beyond those already provided (see https://redhawksdr.github.io/2.2.4/manual/connections/)
New IDL can be added to a REDHAWK instance by creating custom IDL interfaces (https://redhawksdr.github.io/2.2.4/manual/connections/custom-idl-interfaces/)
Recently i've came to an issue to configure Last Participant Support on deployed application. I've found some old post about that:
https://www.ibm.com/developerworks/community/forums/html/topic?id=77777777-0000-0000-0000-000014090728
On server itself i found how to do it. But with jython or wsadmin commands im not able to find how to do it on application itself.
But it does not help for me. Any ideas?
There is no command assistance available for the action of changing last participant support from the admin console which typically implies there is no scripting command associated the action. And there doesn't appear to be an wsadmin AdminApp command to modify the property. Looking at config repo changes made as a result of the admin console action, the IBM Programming Model Extensions (PME) deployment descriptor file "ibm-application-ext-pme.xmi" for an application is created/modified by the action.
If possible, the best long-term solution would be to use a tool like RAD to generate that extensions file when packaging the application because if you need to redeploy the app, your config changes wouldn't get overridden. If you can't mod the app, you can script the addition of an PME descriptor file in each of the desired apps with the knowledge that redeploying the app will overwrite your changes. The changes can be made by doing something along the lines of:
1) create a text file named ibm-application-ext-pme.xmi with contents similar to this:
<pmeext:PMEApplicationExtension xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:pmeext="http://www.ibm.com/websphere/appserver/schemas/5.0/pmeext.xmi" xmi:id="PMEApplicationExtension_1559836881290">
<lastParticipantSupportExtension xmi:id="LastParticipantSupportExtension_1559836881292" acceptHeuristicHazard="false"/>
</pmeext:PMEApplicationExtension>
2) in wsadmin or your jython script do the following (note in this example the xmi file you created is in the current directory, if not, include the full path to it in the createDocument command) :
deployUri = "cells/<your_cell_name>/applications/<your_app_name>.ear/deployments/<your_app_name>/META-INF/ibm-application-ext-pme.xmi"
AdminConfig.createDocument(deployUri, "ibm-application-ext-pme.xmi")
AdminConfig.save()
3) restart the server
I am using sama5d27 som1 ek1 board and I build a Linux kernel for it using yocto project. I open minicom and the system boot. I want to remove debug tweaks from my image features but I must now set a user to my board to login and stop login as a root. How can I add a user to my board ?
You have to use one of the useradd classes. The documentation is there:
https://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#ref-classes-useradd
The meta-skeleton/recipes-skeleton/useradd/useradd-example.bb recipe show you how to do that dynamically.
You can also provide the uids and gids statically by using USERADDEXTENSION = "useradd-staticids" in local.conf or, preferably in your distro and then having files/passwd and files/group anywhere in your BBPATH.
The Option to disable data sharing can be changed at any time by the user:
I want to disable this setting by default for a managed installation of IntelliJ IDEA, ideally via configuration file or registry setting.
How can I do this? I could not find any registry setting or configuration setting so far.
This option is already disabled by default.
The state of the option is stored in the /consentOptions/accepted file under the data directory which is platform specific.
On Windows that would be C:\Users\<user>\AppData\Roaming\JetBrains\consentOptions\accepted.
When the option is enabled, the file will contain something like this:
thrd.plugins:1.0:0:1525589497351;rsch.send.usage.stat:1.1:1:1551998109388
and the following with the option disabled:
thrd.plugins:1.0:0:1525589497351;rsch.send.usage.stat:1.1:0:1551998064076
The format is as follows:
rsch.send.usage.stat:<version>:<enabled>:<timestamp>
You can learn more from the ConsentOptions.java source code.